Closed
Bug 1772007
Opened 4 years ago
Closed 4 years ago
Use plain object for lazy getter in browser/
Categories
(Firefox :: General, task)
Firefox
General
Tracking
()
RESOLVED
FIXED
103 Branch
| Tracking | Status | |
|---|---|---|
| firefox103 | --- | fixed |
People
(Reporter: arai, Assigned: arai)
References
Details
Attachments
(4 files)
Many JSM files define lazy getters on the per-JSM global this object.
The global this object doesn't exist in ES module, and those lazy getters need to be moved to a plain object const lazy = {};, and each consumer needs to be rewritten to refer the lazy getter with lazy.foo.
This migration is done by automated script in bug 1608279.
| Assignee | ||
Updated•4 years ago
|
Summary: Use plain object for lazy getter in browser/actors/ → Use plain object for lazy getter in browser/
| Assignee | ||
Comment 1•4 years ago
|
||
| Assignee | ||
Comment 2•4 years ago
|
||
Depends on D148007
| Assignee | ||
Comment 3•4 years ago
|
||
Depends on D148008
| Assignee | ||
Comment 4•4 years ago
|
||
Depends on D148009
Pushed by arai_a@mac.com:
https://hg.mozilla.org/integration/autoland/rev/b7a722b5f9cf
Part 1: Use plain object for lazy getter in browser/actors/. r=mossop
https://hg.mozilla.org/integration/autoland/rev/7fedadd75117
Part 2: Use plain object for lazy getter in browser/modules/. r=mossop
https://hg.mozilla.org/integration/autoland/rev/e39f280dfcf2
Part 3: Use plain object for lazy getter in browser/themes/. r=desktop-theme-reviewers,dao
https://hg.mozilla.org/integration/autoland/rev/4d318b699cd5
Part 4: Use plain object for lazy getter in browser/tools/mozscreenshots/. r=MattN
Comment 6•4 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/b7a722b5f9cf
https://hg.mozilla.org/mozilla-central/rev/7fedadd75117
https://hg.mozilla.org/mozilla-central/rev/e39f280dfcf2
https://hg.mozilla.org/mozilla-central/rev/4d318b699cd5
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox103:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 103 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•