This patch was autogenerated by my decomponents.py
It covers almost every file with the extension js, jsm, html, py,
xhtml, or xul.
It removes blank lines after removed lines, when the removed lines are
preceded by either blank lines or the start of a new block. The "start
of a new block" is defined fairly hackily: either the line starts with
//, ends with */, ends with {, <![CDATA[, """ or '''. The first two
cover comments, the third one covers JS, the fourth covers JS embedded
in XUL, and the final two cover JS embedded in Python. This also
applies if the removed line was the first line of the file.
It covers the pattern matching cases like "var {classes: Cc,
interfaces: Ci, utils: Cu, results: Cr} = Components;". It'll remove
the entire thing if they are all either Ci, Cr, Cc or Cu, or it will
remove the appropriate ones and leave the residue behind. If there's
only one behind, then it will turn it into a normal, non-pattern
matching variable definition. (For instance, "const { classes: Cc,
Constructor: CC, interfaces: Ci, utils: Cu } = Components" becomes
"const CC = Components.Constructor".)
MozReview-Commit-ID: DeSHcClQ7cG
--HG--
extra : rebase_source : d9c41878036c1ef7766ef5e91a7005025bc1d72b
This was done using the following script:
37e3803c7a/processors/chromeutils-import.jsm
MozReview-Commit-ID: 1Nc3XDu0wGl
--HG--
extra : source : 12fc4dee861c812fd2bd032c63ef17af61800c70
extra : intermediate-source : 34c999fa006bffe8705cf50c54708aa21a962e62
extra : histedit_source : b2be2c5e5d226e6c347312456a6ae339c1e634b0
This was done using the following script:
37e3803c7a/processors/chromeutils-import.jsm
MozReview-Commit-ID: 1Nc3XDu0wGl
--HG--
extra : source : 12fc4dee861c812fd2bd032c63ef17af61800c70
This was done using the following script:
37e3803c7a/processors/chromeutils-import.jsm
MozReview-Commit-ID: 1Nc3XDu0wGl
--HG--
extra : rebase_source : c004a023389f1f6bf3d2f3efe93c13d423b23ccd
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