Closed Bug 781447 Opened 12 years ago Closed 12 years ago

JavaScript content fails to load with "SecurityError" depending on history settings

Categories

(Core :: JavaScript Engine, defect)

All
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 748620

People

(Reporter: bugzilla2, Unassigned)

Details

(Whiteboard: [js:t])

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20100101 Firefox/14.0.1
Build ID: 20120713134347

Steps to reproduce:

Set FF to create a history based on user defined settings.
- Enable creating history
- Enable to save formula data
- Enable to save Cookies
-- Enable to save cookies from third parties
-- Save cookies until: always ask
- Do not delete cookies when FF is closed

Visit a Website that uses some special JavaScript (do not yet know what needs to be in the JS file to make this error happen) like http://www.eatthismuch.com/ or http://www.facebook.com.


Actual results:

FF will produce an error message like this:

SecurityError: The operation is insecure.
http://www.eatthismuch.com/static_files/jscript/compress_js/etm.js
Line: 1


Expected results:

The same what happens when loading this page with the setting "do always create history". The page should load without any errors and all JS files should be loaded.
Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/17.0 Firefox/17.0
Built from http://hg.mozilla.org/mozilla-central/rev/22288130fea2
Build ID: 20120814030521

Confirming that issue is reproducible on latest Nightly.
Status: UNCONFIRMED → NEW
Component: Untriaged → Security
Ever confirmed: true
Hardware: x86_64 → All
Version: 14 Branch → Trunk
Assignee: nobody → general
Component: Security → JavaScript Engine
Product: Firefox → Core
That script is trying to use localStorage.

localStorage is defined to be synchronous, which is not compatible with asking the user whether the data can be stored.  So if you set "Save cookies until: always ask" then localStorage is disabled.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Whiteboard: [js:t]
You need to log in before you can comment on or make changes to this bug.