Open
Bug 709238
Opened 13 years ago
Updated 2 years ago
Secure DOM storage invisible to content script added from chrome
Categories
(Core :: DOM: Core & HTML, defect, P5)
Tracking
()
NEW
People
(Reporter: mozilla, Unassigned)
Details
Until bug 480366 and bug 495747 are fixed, I have been using a content script added from my extension to examine sessionStorage and localStorage. However, if the secure flag is set for a key then my content script cannot see it. For obvious reasons the check restricts visibility of these keys to inner URLs which have scheme https, but this unfortunately excludes chrome URLs. The same thing happens if a localStorage is obtained using getLocalStorageForPrincipal().
Component: General → DOM: Other
Product: Firefox → Core
QA Contact: general → general
|
||
Updated•13 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
|
Assignee | |
Updated•12 years ago
|
Component: DOM: Other → DOM
|
||
Comment 1•7 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046
Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.
If you have questions, please contact :mdaly.
Priority: -- → P5
|
|
Assignee | |
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•