NS_ERROR_DOM_SECURITY_ERR with https://browserid.org/production/browserid.js

RESOLVED WORKSFORME

Status

Mozilla Labs
Identity
RESOLVED WORKSFORME
6 years ago
6 years ago

People

(Reporter: Marc-Aurèle DARCHE, Unassigned)

Tracking

Details

(Whiteboard: [qa+])

(Reporter)

Description

6 years ago
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20100101 Firefox/10.0.1
Build ID: 20120208060813

Steps to reproduce:

- Change default settings:
  Preferences -> Privacy -> History -> Use custom settings for history -> Keep (cookies) until -> "Ask me every time"
- Go to https://browserid.org/signin
- Then this error happens in the JS console:
  Error: uncaught exception: [Exception... "Security error"  code: "1000" nsresult: "0x805303e8 (NS_ERROR_DOM_SECURITY_ERR)"  location: "https://browserid.org/production/browserid.js Line: 8"]


Actual results:

The "Password" field in the Sign In form didn't show after I entered my email address and pressed the "sign in" button, so I couldn't complete the sign-in process.


Expected results:

The "Password" field in the Sign In form should have appeared after I entered my email address and pressed the "sign in" button, so I could complete the sign-in process.
confirming with Seamonkey trunk but unsure if this is a bug in the site itself.
Component: Untriaged → DOM
Product: Firefox → Core
QA Contact: untriaged → general
Component: DOM → Identity
Product: Core → Mozilla Labs
QA Contact: general → identity
Version: 10 Branch → unspecified
See related https://bugzilla.mozilla.org/show_bug.cgi?id=365772 (and others).
It can be triggered simply with 'Ask every time' cookies, and this js:

<script>var s = localStorage;</script> <-- throws -->
https://github.com/mozilla/browserid/pull/1106 will probably cover this exception.
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 4

6 years ago
Confirming, this causes me to no longer be able to log in to MDN :(

When will the fix from comment 3 be applied?
Whiteboard: [qa+]
(Reporter)

Comment 5

6 years ago
I have checked with both Firefox 10.0.1 (the stable version by the time of this bug report) and Firefox 13.0 (the current stable version) and the reported problem is not happening again. So I am happy to mark this ticket as resolved :-)
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.