Closed
Bug 1000068
Opened 11 years ago
Closed 11 years ago
Accessing localStorage from Add-on content scripts throws "The operation is insecure."
Categories
(Add-on SDK Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 980023
mozilla29
People
(Reporter: petrasb, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 20140421221237
Steps to reproduce:
Our Add-on uses localStorage to store user data in website context. It access localStorage via injected content scripts using standard methods:
localStorage.getItem(key);
localStorage.setItem(key, value);
Code is injected to website via PageMod:
pageMod.PageMod({
contentScriptFile: [
self.data.url("app.js")
]})
Additional info:
We are using Addon SDK 1.16
Problem occurs since FF 29.0 beta (everything works with FF 28)
Actual results:
When methods getItem/setItem are called, security exception is thrown: [Exception... "The operation is insecure." code: "18" nsresult: "0x80530012 (SecurityError)" location: "<unknown>"]
Expected results:
Value should be stored in (read from) local storage.
| Reporter | ||
Updated•11 years ago
|
Component: Untriaged → Security
Comment 1•11 years ago
|
||
Jorge, any idea who to CC here?
Component: Security → Extension Compatibility
Flags: needinfo?(jorge)
Comment 2•11 years ago
|
||
A direct link to the addon in question:
https://dragdis.com/Public/extensions/firefox/dragdis.xpi
It's not available yet on http://addons.mozilla.org
Updated•11 years ago
|
Component: Extension Compatibility → General
Flags: needinfo?(jorge)
Product: Firefox → Add-on SDK
Target Milestone: --- → mozilla29
Version: 29 Branch → unspecified
Comment 3•11 years ago
|
||
Might be related to the SDK, so I'm moving it there first.
Flags: needinfo?(gkrizsanits)
Comment 4•11 years ago
|
||
I've landed a patch for this problem, it should be fixed in ff30.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Flags: needinfo?(gkrizsanits)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•