Closed
Bug 1789202
Opened 5 months ago
Closed 5 months ago
Expose ChromeUtils to all DevTools modules
Categories
(DevTools :: General, task)
DevTools
General
Tracking
(firefox106 fixed)
RESOLVED
FIXED
106 Branch
Tracking | Status | |
---|---|---|
firefox106 | --- | fixed |
People
(Reporter: ochameau, Assigned: ochameau)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
In order to help the migration of the DevTools codebase to ES Modules (bug 1525652), we should be exposing ChromeUtils
to all modules.
This symbol is being made available to all privileged ES Modules.
Assignee | ||
Comment 1•5 months ago
|
||
This will help transition to ES Modules as this symbol is exposed to them.
$ sed -ie "/require(.ChromeUtils.)/d" $(git grep -l 'require("ChromeUtils")' devtools/)
$ sed -ie "/loader.lazyRequireGetter(this, .ChromeUtils./d" $(git grep -l 'loader.lazyRequireGetter(this, "ChromeUtils"' devtools/)
- the edition of builtin-modules.js + eslintrc.js + manual eslint fixes
Updated•5 months ago
|
Assignee: nobody → poirot.alex
Status: NEW → ASSIGNED
Pushed by apoirot@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/8e320b5393ee [devtools] Expose ChromeUtils as a global to all DevTools modules. r=perftest-reviewers,nchevobbe,AlexandruIonescu
Comment 3•5 months ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 5 months ago
status-firefox106:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 106 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•