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)

8 Branch
x86
Linux
defect

Tracking

()

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
Status: UNCONFIRMED → NEW
Ever confirmed: true
Component: DOM: Other → DOM
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
Component: DOM → DOM: Core & HTML
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.