Most of the codebase that needs to create a debugger server
can use a server with all actors registered.
Define an additional method registerAllActors to do that.
By previous implementations, all the call sites that were
using browser: true were indirectly using tab & root: true
as well. So all the call sites using browser: true have been
migrated to registerAllActors and the specific behavior of
the browser: true case has been removed. Passing browser:true
to registerActors now only registers browser specific actors.
MozReview-Commit-ID: F3sx71eGrdG
--HG--
extra : rebase_source : 7704264e84d96e03a0c789103ff466980913d4d2
DebuggerServer has old APIs addBrowserActors & addTabActors that can be
replaced by calls to registerActors.
MozReview-Commit-ID: KpYJpbSHM8I
--HG--
extra : rebase_source : c7f20edf503b944ef2582b5fe73bd6d899c0d1cc
The devtools.onboarding.experiment pref now supports 3 states:
- off (default)
- on
- force
When set to "on" or "force" the preference will flip devtools
enabled to false.
When set to "force" the devtools.enabled pref can no longer be
flipped to true by looking at devtools.selfxss.count, users
have to go through the onboarding flow.
To make sure the devtools.enabled pref is only flipped once, we
use a supporting pref devtools.onboarding.experiment.flipped
MozReview-Commit-ID: B5fPKuGxPW2
--HG--
extra : rebase_source : 6da6cc41f6388871cdfc66c04bef3b54ccfabcbf
Add localization notes to aboutdevtools.dtd and move it back to the locales
folder where it can be picked up by localization teams.
MozReview-Commit-ID: 8fDimFwdBXv
--HG--
rename : devtools/shim/aboutdevtools/tmp-locale/aboutdevtools.dtd => devtools/shim/locales/en-US/aboutdevtools.dtd
extra : rebase_source : a39410806d2fc930eaaf74c7894371aa041b0dfe
The welcome message used to be defined in DTD. Since it has a dynamic part (the
toggle toolbox shortcut) it's easier for localization purposes to have it in a
properties file and dynamically insert it.
MozReview-Commit-ID: FhgQjbs8Dw0
--HG--
extra : rebase_source : 35efe9ccd3ce17931edbba5e0deac32c81fc7609
This changeset adds 3 scalars:
- devtools.aboutdevtools.opened -> logged every time the page is loaded
- devtools.aboutdevtools.installed -> logged when the user clicks on the
install button
- devtools.aboutdevtools.noinstall_exits -> logged when leaving the page
if devtools is not enabled
And 2 keyed histograms:
- DEVTOOLS_ABOUT_DEVTOOLS_OPENED_REASON (is it a shortcut, is it a menu
item etc...)
- DEVTOOLS_ABOUT_DEVTOOLS_OPENED_KEY (in case of a keyshortcut, what is
the keyshortcut id)
MozReview-Commit-ID: 1DET1ozf8i4
--HG--
extra : rebase_source : f2f96e29a8849dec83b03d6daacbf6c6ca7fce2f
This changeset adds 3 scalars:
- devtools.aboutdevtools.opened -> logged every time the page is loaded
- devtools.aboutdevtools.installed -> logged when the user clicks on the
install button
- devtools.aboutdevtools.noinstall_exits -> logged when leaving the page
if devtools is not enabled
And 2 keyed histograms:
- DEVTOOLS_ABOUT_DEVTOOLS_OPENED_REASON (is it a shortcut, is it a menu
item etc...)
- DEVTOOLS_ABOUT_DEVTOOLS_OPENED_KEY (in case of a keyshortcut, what is
the keyshortcut id)
MozReview-Commit-ID: 1DET1ozf8i4
--HG--
extra : rebase_source : 5038fcb6741653b7f66581cd601ba9dea58a847f
A close button on the starting page of the devtools onboarding flow
will be helpful for users who triggered the shortcut by mistake and
would like to escape the flow.
MozReview-Commit-ID: 7rZ50jFepJ3
--HG--
extra : rebase_source : 9f0dadf3a68f084d05e9f0098a8a7ac90becf964
Add a footer containing a link to download Firefox developer
edition in about:devtools after devtools have been enabled.
MozReview-Commit-ID: KFefF6qB9tO
--HG--
extra : rebase_source : 73155c83264bfb26ca25dfc9c7a2fc6f4655f460
The FrameLoaderOwner interface has been implemented in WebIDL for several
years now, so these QIs are simply unnecessary overhead.
MozReview-Commit-ID: LAzvfm5Qhy0
--HG--
extra : rebase_source : 2495c07df21c474f5fabc257ff4db43b0d8047e4