Closed
Bug 394352
Opened 17 years ago
Closed 17 years ago
protect navigator.offlineResources with a permission
Categories
(Core :: DOM: Core & HTML, defect, P2)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
DUPLICATE
of bug 402272
People
(Reporter: dcamp, Assigned: dcamp)
References
Details
Attachments
(2 files)
8.44 KB,
patch
|
jst
:
review+
jst
:
superreview+
|
Details | Diff | Splinter Review |
1.25 KB,
patch
|
jst
:
review+
|
Details | Diff | Splinter Review |
Since navigator.offlineResources lets sites pin data on the user's disk, it should probably be protected by a permission. The attached patch throws a security exception when the API is accessed without the necessary permissions.
Flags: blocking1.9?
Attachment #278997 -
Flags: superreview?(jst)
Attachment #278997 -
Flags: review?(jst)
Assignee: nobody → dcamp
Flags: blocking1.9? → blocking1.9+
Updated•17 years ago
|
Attachment #278997 -
Flags: superreview?(jst)
Attachment #278997 -
Flags: superreview+
Attachment #278997 -
Flags: review?(jst)
Attachment #278997 -
Flags: review+
Attachment #278997 -
Flags: approval1.9+
Assignee | ||
Comment 1•17 years ago
|
||
this fix is needed to fix the tests after adding the permission.
Attachment #284687 -
Flags: review?(jst)
Updated•17 years ago
|
Attachment #284687 -
Flags: review?(jst) → review+
Assignee | ||
Comment 2•17 years ago
|
||
Comment on attachment 278997 [details] [diff] [review] protect offline apps with a permission Clearing the approval flag. This is going to get caught up in the upcoming API changes, and this doesn't make sense to commit without UI to manage the permission anyway.
Attachment #278997 -
Flags: approval1.9+
Dcamp, what's going on here? Shouldn't we land this to let the UI folks build on it? What priority do you think this should have?
Priority: -- → P2
Assignee | ||
Comment 4•17 years ago
|
||
This patch has ended up as part of the patch for bug 402272, so we can probably close this bug...
Sold!
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Updated•11 years ago
|
Component: DOM: Mozilla Extensions → DOM
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•