Closed
Bug 1416622
Opened 7 years ago
Closed 7 years ago
Tighten up libpref's process checking
Categories
(Core :: Preferences: Backend, enhancement)
Core
Preferences: Backend
Tracking
()
RESOLVED
FIXED
mozilla59
People
(Reporter: n.nethercote, Assigned: n.nethercote)
References
Details
Attachments
(1 file)
libpref's "parent process only" checking is a bit inconsistent at the moment.
Comment hidden (mozreview-request) |
Assignee | ||
Updated•7 years ago
|
Blocks: prefs-cleanup
Comment 2•7 years ago
|
||
mozreview-review |
Comment on attachment 8927705 [details] Bug 1416622 - Tighten up libpref's process checking. https://reviewboard.mozilla.org/r/198980/#review204410 ::: modules/libpref/Preferences.cpp:3079 (Diff revision 1) > - // TODO: this should really assert because you can't set prefs in a > - // content process. But so much code currently does this that we just > - // ignore it for now. > + // This path is hit a lot when setting up prefs for content processes. Just > + // ignore it in that case, because content processes aren't responsible for > + // saving prefs. It seems the todo item should be kept in some form (it's still a worthwhile goal to assert here)
Attachment #8927705 -
Flags: review?(mh+mozilla) → review+
Assignee | ||
Comment 3•7 years ago
|
||
> It seems the todo item should be kept in some form (it's still a worthwhile
> goal to assert here)
I deliberately removed it because I thought it wasn't a worthwhile goal -- this function is low-level enough that I can't see a better way to handle things than with this check...
Assignee | ||
Comment 4•7 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/3328527cb7d5a4fc3df2abe1a613e13faaad364f Bug 1416622 - Tighten up libpref's process checking. r=glandium
Comment 5•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/3328527cb7d5
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox59:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla59
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → n.nethercote
Updated•7 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•