Persistent listeners for onMessage and onConnect are special because they
don't have parent EventManagers, so we have a lot of custom code just to keep
track of which extensions have registered them during previous runs.
In this patch, I simplify all that logic to always assume that any extension
which sends messages from content scripts has those listeners setup properly.
The only observable difference is that some poorly written extensions which
were previously broken by delayed startup will now "work" by being started
earlier if a message from a content script arrives during browser startup.
Additionally, unconfuse two different meanings of the "startup" event.
Bonus, avoid some logspam during tests.
Differential Revision: https://phabricator.services.mozilla.com/D70955
Only 3 callers are using a non-UTF-8 charset as the first parameter.
* MediaDocument.cpp: This does not make sense because the "filename" part of
URLs will always be encoded with UTF-8.
* nsContextMenu.js: This is wrong because "mailto:" URLs don't care about the
document charset.
* Finder.jsm: This caused bug 1623222.
Differential Revision: https://phabricator.services.mozilla.com/D67386
--HG--
extra : moz-landing-system : lando
This patch does the following:
* Moves most logic for initiating about:home / about:newtab into AboutNewTab.jsm
* Makes AboutNewTab the API surface for overriding the default about:newtab URLs.
* Reduces the surface of nsIAboutNewTabService, and makes the properties read-only
* Splits the remaining code in the nsIAboutNewTabService into an implementation for
the parent process, and one for content processes.
This split will hopefully help reduce confusion about which code in
AboutNewTabService is running in which process.
Differential Revision: https://phabricator.services.mozilla.com/D65569
--HG--
rename : browser/components/newtab/test/xpcshell/test_AboutNewTabService.js => browser/components/newtab/test/xpcshell/test_AboutNewTab.js
extra : moz-landing-system : lando
This patch does the following:
* Moves most logic for initiating about:home / about:newtab into AboutNewTab.jsm
* Makes AboutNewTab the API surface for overriding the default about:newtab URLs.
* Reduces the surface of nsIAboutNewTabService, and makes the properties read-only
* Splits the remaining code in the nsIAboutNewTabService into an implementation for
the parent process, and one for content processes.
This split will hopefully help reduce confusion about which code in
AboutNewTabService is running in which process.
Differential Revision: https://phabricator.services.mozilla.com/D65569
--HG--
rename : browser/components/newtab/test/xpcshell/test_AboutNewTabService.js => browser/components/newtab/test/xpcshell/test_AboutNewTab.js
extra : moz-landing-system : lando
Add new zoomSiteSpecific and zoomFullPage settings in browserSettings API
Updated description of zoomSiteSpecific in brower_settings.json
Differential Revision: https://phabricator.services.mozilla.com/D59433
--HG--
extra : moz-landing-system : lando
Summary
Before the changes, if an mozilla addons theme was applied and an theme extension api has been called which call theme.reset() from background.js script then the browser theme was getting reset, which
should'nt happen. Code changes made in toolkit/components/extension/parent/ext-theme.js
Differential Revision: https://phabricator.services.mozilla.com/D58095
--HG--
extra : moz-landing-system : lando
Added right click on new tab button to open containers menu.
Removed long press and added option to enable left click in preferences menu.
Renamed privacy.userContext.longPressBehavior to privacy.userContext.newTabContainer.enabled
Differential Revision: https://phabricator.services.mozilla.com/D58410
--HG--
extra : moz-landing-system : lando
I also took the opportunity to fix the SSL proxy label - we shouldn't label
things "SSL" anymore in 2019, unless they really are. All the comments in
bug 969282, bug 1577862 and bug 1601871 use 'HTTPS'.
Differential Revision: https://phabricator.services.mozilla.com/D58120
--HG--
extra : moz-landing-system : lando
I also took the opportunity to fix the SSL proxy label - we shouldn't label
things "SSL" anymore in 2019, unless they really are. All the comments in
bug 969282, bug 1577862 and bug 1601871 use 'HTTPS'.
Differential Revision: https://phabricator.services.mozilla.com/D58120
--HG--
extra : moz-landing-system : lando