Closed
Bug 1187419
Opened 9 years ago
Closed 9 years ago
SettingsRequestManager should only be loaded in parent process
Categories
(Core :: DOM: Device Interfaces, defect)
Core
DOM: Device Interfaces
Tracking
()
RESOLVED
FIXED
mozilla42
Tracking | Status | |
---|---|---|
firefox42 | --- | fixed |
People
(Reporter: gerard-majax, Assigned: gerard-majax)
References
Details
(Whiteboard: [systemsfe])
Attachments
(1 file)
2.38 KB,
patch
|
gwagner
:
review+
|
Details | Diff | Splinter Review |
While we would want this to work, for now it's partly broken. As explained on bug 1181561 comment 26: - settings.js loads SettingsRequestManager.jsm in parent - in content, add an observer against a setting - have chrome code living in content that uses SettingsService to set the same setting Expected: Content observer is triggered Actual: No observer is triggered on content side. A quick patch to avoid anyone loosing time on this issue will be to deny loading SettingsRequestManager in content process
Assignee | ||
Comment 1•9 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=f05b63a4e82a
Attachment #8638711 -
Flags: review?(anygregor)
Updated•9 years ago
|
Attachment #8638711 -
Flags: review?(anygregor) → review+
Assignee | ||
Updated•9 years ago
|
Keywords: checkin-needed
Comment 3•9 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/ae9f773bab88
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox42:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla42
Updated•9 years ago
|
Whiteboard: [systemsfe]
You need to log in
before you can comment on or make changes to this bug.
Description
•