nsXULWindow is no longer XUL specific and is somewhat confusing name.
Differential Revision: https://phabricator.services.mozilla.com/D51486
--HG--
rename : xpfe/appshell/nsXULWindow.cpp => xpfe/appshell/AppWindow.cpp
rename : xpfe/appshell/nsXULWindow.h => xpfe/appshell/AppWindow.h
rename : xpfe/appshell/nsIXULWindow.idl => xpfe/appshell/nsIAppWindow.idl
extra : moz-landing-system : lando
nsXULWindow is no longer XUL specific and is somewhat confusing name.
Differential Revision: https://phabricator.services.mozilla.com/D51486
--HG--
rename : xpfe/appshell/nsXULWindow.cpp => xpfe/appshell/AppWindow.cpp
rename : xpfe/appshell/nsXULWindow.h => xpfe/appshell/AppWindow.h
rename : xpfe/appshell/nsIXULWindow.idl => xpfe/appshell/nsIAppWindow.idl
extra : moz-landing-system : lando
nsXULWindow is no longer XUL specific and is somewhat confusing name.
Differential Revision: https://phabricator.services.mozilla.com/D51486
--HG--
rename : xpfe/appshell/nsXULWindow.cpp => xpfe/appshell/AppWindow.cpp
rename : xpfe/appshell/nsXULWindow.h => xpfe/appshell/AppWindow.h
rename : xpfe/appshell/nsIXULWindow.idl => xpfe/appshell/nsIAppWindow.idl
extra : moz-landing-system : lando
This was added in bug 1559697 , to show the Close button on macOS.
It had unwanted side effects, including the appearance of buttons
that don't have any apparent effect. To resolve this regression,
the change is undone.
Differential Revision: https://phabricator.services.mozilla.com/D49746
--HG--
extra : moz-landing-system : lando
Webextension api to get memory usage. Also brings back memory.jsm, as it is used by the api. Adds test_ext_memory.js to test ext-memory.js' functionality and permissions.
Differential Revision: https://phabricator.services.mozilla.com/D38536
--HG--
extra : moz-landing-system : lando
In the old way, if referrer is ommited we will not be able to go to
download page. In that case, we should use originalReferrer in
ReferrerInfo object
Differential Revision: https://phabricator.services.mozilla.com/D39875
--HG--
extra : moz-landing-system : lando
This changes provide basic support for webextenion tabs and webNavigation listeners by implementing missing objects on which Fennec implementation was relying.
Differential Revision: https://phabricator.services.mozilla.com/D36575
--HG--
extra : moz-landing-system : lando
This changes provide basic support for webextenion tabs and webNavigation listeners by implementing missing objects on which Fennec implementation was relying.
Differential Revision: https://phabricator.services.mozilla.com/D36575
--HG--
extra : moz-landing-system : lando
Previously, the network.webRTCIPHandlingPolicy "disable_non_proxied_udp" only
enabled the use of WebRTC if a proxy was configured and the WebRTC service
supported TURN TCP.
This aims to match Chrome's behavior by forcing the use of a proxy if one is
configured, otherwise falling back to mode 3 (no host candidates and default
route only).
Also, remove some dead code left over from the old way of routing TURN
communications through an HTTP proxy.
Differential Revision: https://phabricator.services.mozilla.com/D37892
--HG--
extra : moz-landing-system : lando
Bug 1547669 added some things to the top sites API, but it turned out to be not quite what we (the quantumbar team) needed (see bug 1568617). What we need is the list of top sites exactly as it appears on newtab. That list is determined by activity stream, which lives in browser. But the top sites API lives in toolkit.
There was an earlier, now abandoned revision for that bug [1] where it was suggested that top sites be moved to browser. So we should do that.
[1] https://phabricator.services.mozilla.com/D36200
Differential Revision: https://phabricator.services.mozilla.com/D39589
--HG--
rename : toolkit/components/extensions/parent/ext-topSites.js => browser/components/extensions/parent/ext-topSites.js
rename : toolkit/components/extensions/schemas/top_sites.json => browser/components/extensions/schemas/top_sites.json
rename : toolkit/components/extensions/test/xpcshell/test_ext_topSites.js => browser/components/extensions/test/xpcshell/test_ext_topSites.js
extra : moz-landing-system : lando
Removing the lwt aliases from the theme API schema is not going to be enough, because the images and colors properties are very permissive on the unknown properties (likely to prevent a property supported on chrome but not on firefox to prevent the theme from being installed), and so removing the lwt aliases from the schema would not raise any error (the theme API implementation would just be silently ignoring the deprecated lwt aliases).
For the above reason the following patch use the following approach:
- kept the deprecated lwt aliases in the schema, but changes the deprecation warning message to mention that the property is now completely ignored by Firefox, and which property should be used instead
- removed the deprecation warning from the toolbar_text theme colors property, as we decided that we are not going to deprecate it anymore
- changed the theme API implementation to ignore the deprecated lwt alias property
- repurposed browser_ext_themes_lwtsupport.js test file to verify that the lwt aliases are ignored as expected
A separate addons-linter pull request is going to be created, to ensure that the addons-linter will raise linting errors (instead of linting warning) when these deprecated lwt aliases are being used in a theme (to prevent that newly submitted theme versions including the aliases will go unnoticed).
Depends on D37890
Differential Revision: https://phabricator.services.mozilla.com/D37891
--HG--
extra : moz-landing-system : lando
Besides fixing the "privateBrowsing" flag, this patch also ensures that
notifications are correctly erased if they were closed during the call
into nsIAlertsService, because nsIAlertsService.idl documents that the
"alertfinished" callback may be called immediately.
Differential Revision: https://phabricator.services.mozilla.com/D37393
--HG--
extra : moz-landing-system : lando
On Windows, Linux, Android, the backend for native notifications closes
the notification notification upon click.
On macOS, the notification sticks around, unless the user closes the
notification. This behavior is also observed in the Notification API
on the web platform, across different browsers.
Differential Revision: https://phabricator.services.mozilla.com/D37149
--HG--
extra : moz-landing-system : lando
Adds includePinned and includeSearchShortcuts options to the topSites API, so
that it's possible to get a list of results like it's shown on the newtab page.
Both options default to false, so that the existing behavior is preserved.
The API gets disabled on Android; this API always depended on APIs not well
supported there, and the test is disabled on Android, so it was untested.
Differential Revision: https://phabricator.services.mozilla.com/D36467
--HG--
extra : moz-landing-system : lando
This API allows consumers to save a recorded profile directly to a
file. It will be located under the "profiler" sub folder inside the
user's profile.
Differential Revision: https://phabricator.services.mozilla.com/D32146
--HG--
extra : moz-landing-system : lando
Adds includePinned and includeSearchShortcuts options to the topSites API, so
that it's possible to get a list of results like it's shown on the newtab page.
Both options default to false, so that the existing behavior is preserved.
The API gets disabled on Android; this API always depended on APIs not well
supported there, and the test is disabled on Android, so it was untested.
Differential Revision: https://phabricator.services.mozilla.com/D36467
--HG--
extra : moz-landing-system : lando
Previous implementation created new DownloadItem with a null as an indirect result of list.add()
Differential Revision: https://phabricator.services.mozilla.com/D34305
--HG--
extra : moz-landing-system : lando
Checking extension.shutdownReason for any purpose other than detecting
app shutdown is unreliable, since actions such as disabing, uninstalling,
etc. may happen ito an extension after it has shut down. Remove the
temptation for api authors to write incorrect code by removing
extension.shutdownReason and replacing it with an isAppShutdown boolean
passed to shutdown handlers.
Differential Revision: https://phabricator.services.mozilla.com/D30605
--HG--
extra : rebase_source : 07ff7710757150d011fec6bc3ed134c6509e9a12
nsITabParent is exposed to frontend code and is generally used as a representation of a remote tab. We could just rename the interface to nsIBrowserParent and worry about it later, but I think it's better to rename the interface to nsIRemoteTab so that we can later work on splitting the interface away from the PBrowser protocol.
Note: Some frontend code refers to a TabParentId. This commit renames this to RemoteTabId. We need to figure out the purpose of TabId with fission.
Differential Revision: https://phabricator.services.mozilla.com/D28132
--HG--
rename : dom/interfaces/base/nsITabParent.idl => dom/interfaces/base/nsIRemoteTab.idl
extra : rebase_source : 9d8a1790a7bb10195ad063644d1a93d63b2afb72
Bug 1495072 uncovered a race in the webextension persistent listener logic
where the Promise returned by a listener that is not re-registered during
extension startup may never resolve. When this occurs with a blocking
webRequest listener, content loads just hang forever.
Fix this by forcing primed listeners to reject is they are invoked after
the background page has started.
Differential Revision: https://phabricator.services.mozilla.com/D27942
--HG--
extra : rebase_source : f6179911291348c6a0ed99609bbc5fe5526eaa74
To correctly present IPv6 URL, we need to add the brackets for the host obtained from nsIURI
Differential Revision: https://phabricator.services.mozilla.com/D21828
--HG--
extra : moz-landing-system : lando
The static theme startup code is both super asynchronous and super
inefficient. It currently takes a noticeable amount of time after startup to
finish its work and apply its theme, which results in the user seeing a flash
of the default theme before their selected them is applied.
This is particularly noticeable when dark mode themes are enabled.
This patch caches the fully-processed theme data in the addonStartup cache,
and applies it immediately after extension startup begins, if it's available.
--HG--
extra : rebase_source : fd2f7de75dda67063eb9bc4dc3e39171eb150de9
extra : histedit_source : 945054c6320280a3b5a0ca1afc24c33e7e584325