These issues were previously ignored due to the nature of our global import
rules. They need to be fixed before that rule can be updated.
MozReview-Commit-ID: DCChktTc5TW
Extract all the logic that will be shared between about debugging and the application
panel to a dedicated client module.
MozReview-Commit-ID: Ccnmp3dCZpW
Extract all the logic that will be shared between about debugging and the application
panel to a dedicated client module.
MozReview-Commit-ID: Ccnmp3dCZpW
Extract all the logic that will be shared between about debugging and the application
panel to a dedicated client module.
MozReview-Commit-ID: Ccnmp3dCZpW
Since gBrowser is going to become a plain JS object instead of a DOM node,
we don't want any callers directly referring to the DOM node to get ahold of it.
MozReview-Commit-ID: KbE5dlTWmS
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
DebuggerServer.init() already bails out if it was previously initialized
so we could avoid guarding the calls to init() with it everywhere.
Registering an actor module several times is also a noop as the Server
keeps a map of all the already registered modules and will bail out if
the module is already known.
MozReview-Commit-ID: 4ONLlx9253i
This removes the switching based on the RDM.html pref and the pref itself.
Some files in old RDM are updated for completeness, but they are about to be
removed anyway.
MozReview-Commit-ID: JnTC7ZF3UCC
This removes the switching based on the RDM.html pref and the pref itself.
Some files in old RDM are updated for completeness, but they are about to be
removed anyway.
MozReview-Commit-ID: JnTC7ZF3UCC
As devtools become optional, nsContextMenu needs to check if devtools are installed before
displaying the devtools-related menu entries.
Rather than loading devtools classing and calling APIs, use APIs provided by the DevToolsShim,
that will stay in mozilla-central.
MozReview-Commit-ID: CxqabTjhckC
This changeset modifies devtools-browser.css to import:
- commandline-browser.css (needed for GCLI)
- responsivedesign.css (needed for the old RDM)
These files are no longer included in the main browser.css files.
devtools-browser.css is also no longer loaded by browser.xul.
Instead it is dynamically loaded when devtools need the browser stylesheet:
- when creating a side or bottom host (need the splitter)
- when opening gcli
- when opening the old responsive design
devtools-browser.js keeps track of the browser stylesheets loaded in the
various tracked windows and will remove the stylesheet when the window is unloaded.
MozReview-Commit-ID: AL3CxS7mvdO