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)

Product:
Core
Component:
DOM: Device Interfaces
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla42
Tracking Flags:
Tracking Status
firefox42 --- fixed

People

(Reporter: gerard-majax, Assigned: gerard-majax)

References

Details

(Whiteboard: [systemsfe])

Attachments

(1 file)

Make sure SettingsRequestManager is only loaded in parent
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
Blocks: 1187422
Attachment #8638711 - Flags: review?(anygregor) → review+
Keywords: checkin-needed
https://hg.mozilla.org/mozilla-central/rev/ae9f773bab88
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox42: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla42
Whiteboard: [systemsfe]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: