As we add more behaviors to EventManager, the signature of the constructor
is going to get really clumsy. Head that off by converting it to take a
general parameters object.
This introduces a compatibility problem for existing webextension experiments,
put in a backward-compatibility shim for now.
MozReview-Commit-ID: 72QDfiwRm5j
--HG--
extra : rebase_source : 31c3fd561f373a5d75c4336de830aa5a2abfe797
We will be moving existing generic preferences for devtools from libpref/init/all.js
to a new preferences file that will be devtools/preferences/devtools.js and that
will always be shipped. We rename the current devtools.js to devtools-client.js to
avoid conflicts when packaging the preference file to @RESPATH@/browser/@PREF_DIR@/devtools.js
MozReview-Commit-ID: INnqWGBoIAF
--HG--
rename : devtools/client/preferences/devtools.js => devtools/client/preferences/devtools-client.js
extra : rebase_source : c6c3fefbedda04792b7d48d398e40c816316e320
Changing the name for consistency purposes (see RFC
https://github.com/devtools-html/rfcs/issues/43)
MozReview-Commit-ID: EahEwoR9eBF
--HG--
rename : devtools/startup/devtools-startup-prefs.js => devtools/startup/preferences/devtools-startup.js
extra : rebase_source : 5aeb6fa4d1264de91097bf29f9aace844e84ee04
Changing the name for consistency purposes (see RFC
https://github.com/devtools-html/rfcs/issues/43)
MozReview-Commit-ID: BBXObtPaR00
--HG--
rename : devtools/client/webide/webide-prefs.js => devtools/client/webide/preferences/webide.js
extra : rebase_source : 33e24e37b9ec375684f3248ea9e4c200fad71856
Loading this script into every frameloader wasts a massive amount of memory in
every content process, even though it's only needed when we load about:home or
about:newtab.
MozReview-Commit-ID: 5YtEKLGVX4
--HG--
rename : browser/extensions/onboarding/content/onboarding.js => browser/extensions/onboarding/content/Onboarding.jsm
extra : rebase_source : 6592a7ce188cbab5682242d6783883726788130b
extra : amend_source : 6da2cfd3c630e20a7e8b089bbff1403378f5acc3
Contexts for active extension views are kept in a Set on the owning extension.
That list is meant to be kept current, with views added and removed as they're
created and unloaded. A refactoring at some point in the past, though, changed
that so that we only cleaned up parent views at extension shutdown, not at
view shutdown.
MozReview-Commit-ID: FW8KHPOD9qc
--HG--
extra : rebase_source : fab255ba2fb5ee55be41c252c89930d38f6edbe8
extra : amend_source : 54863d79a1d571a7354aa15f74e2fc4448297777
Creating the temporary panel for a pre-load popup can be expensive, especially
for OOP popups, where we need to create a compositor. Since we currently need
to create a pre-load popup every time we hover over a browser action with a
popup, it's probably worth saving and re-using them, rather than always
creating a new one.
MozReview-Commit-ID: GwG7qJNdk8f
--HG--
extra : rebase_source : 9d8f139167b6cad8047c3ac75e5ff84886c27da2
extra : source : 29b2567d16eb2d8d58da6e3b616c42eebb0de9f1
This also aligns the help button to the bottom of the window even when the meta tree is hidden.
MozReview-Commit-ID: GCmgThN569z
--HG--
extra : rebase_source : 0dba1f8b8f84d5d97706a283560a3a3c6d7278d8
Cleanup of all localization notes that refer to entities
that are not listed in the corresponding localization file.
MozReview-Commit-ID: Bl0VU9HoPfa
--HG--
extra : rebase_source : 86680b8ae037783304f045e94c7af7053a0f69e9