Closed
Bug 808327
Opened 13 years ago
Closed 13 years ago
[settings] Re-enable security checks for settings.
Categories
(Core :: DOM: Device Interfaces, defect)
Tracking
()
People
(Reporter: gwagner, Assigned: gwagner)
References
Details
Attachments
(1 file, 1 obsolete file)
|
1.01 KB,
patch
|
bent.mozilla
:
review+
|
Details | Diff | Splinter Review |
We have no good way to check indexedDB-chrome-settings-read and indexedDB-chrome-settings-write when we access the settings DB via the SettingsService.
|
Assignee | |
Updated•13 years ago
|
blocking-basecamp: --- → ?
I thought we only use this in one place, to read gps enable/disable?
I talked with dougt and he's going to investigate here.
|
||
Updated•13 years ago
|
Assignee: nobody → anygregor
blocking-basecamp: ? → +
|
|
Assignee | |
Updated•13 years ago
|
Summary: [settings] Fix SettingsService use in chrome code → [settings] Re-enable security checks for settings.
|
|
Assignee | |
Comment 3•13 years ago
|
||
|
|
Assignee | |
Comment 4•13 years ago
|
||
Attachment #679432 -
Attachment is obsolete: true
|
|
Assignee | |
Updated•13 years ago
|
Attachment #679434 -
Flags: review?(bent.mozilla)
|
||
Updated•13 years ago
|
Attachment #679434 -
Flags: review?(bent.mozilla) → review+
|
|
Assignee | |
Comment 5•13 years ago
|
||
|
||
Comment 6•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla19
|
||
Comment 7•13 years ago
|
||
status-firefox18:
--- → fixed
status-firefox19:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•