Closed
Bug 1765427
Opened 3 years ago
Closed 3 years ago
initializedModules in BrowserGlue are never initialised
Categories
(Firefox :: General, defect, P3)
Firefox
General
Tracking
()
RESOLVED
FIXED
101 Branch
| Tracking | Status | |
|---|---|---|
| firefox101 | --- | fixed |
People
(Reporter: standard8, Assigned: standard8)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
The initializedModules in BrowserGlue are never initialised - because they are using lazy getters and nothing triggers them, they never get triggered.
This is also demonstrated by the fact that ContentPrefServiceParent.alwaysInit was removed in bug 1645538 but hasn't been throwing.
Bug 1765418 is handling the UpdateListener case, this bug can handle removing the remains.
|
Assignee | |
Comment 1•3 years ago
|
||
Depends on D144060
Pushed by mbanner@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/9c48b6682930
Remove initializedModules from BrowserGlue as they don't actually work. r=mak
|
||
Comment 3•3 years ago
|
||
Backed out 2 changesets (bug 1765418, bug 1765427) for causing bc failures in browser_doorhanger_bc_check_unsupported.
Backout link: https://hg.mozilla.org/integration/autoland/rev/d9abb49c107bfa10a2623d71d0956affe67cc1c6
Flags: needinfo?(standard8)
|
|
Assignee | |
Updated•3 years ago
|
Flags: needinfo?(standard8)
Pushed by mbanner@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ee0ab9901b3c
Remove initializedModules from BrowserGlue as they don't actually work. r=mak
|
||
Comment 5•3 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox101:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 101 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•