Closed
Bug 1102372
Opened 11 years ago
Closed 7 years ago
if navigator.mozId.watch triggers a password prompt, onready never fires
Categories
(Firefox OS Graveyard :: FxA, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: nick, Unassigned)
References
Details
Due to https://bugzilla.mozilla.org/show_bug.cgi?id=1028398, navigator.mozId.watch will trigger a PW prompt. If the closes this dialog box, onready never fires. This makes implementing an authentication scheme with FxA difficult, since usually I would wait for onready before trying to contact the verifier (since network requests seem to fail during app start up), but now there's the possibility that onready is never called.
| Reporter | ||
Comment 1•11 years ago
|
||
If the user does enter their password, onlogin fires, then onready. This seems in line from the case where the user has been logged into this app before.
Comment 2•11 years ago
|
||
(In reply to Nick Desaulniers [:\n] from comment #1)
> If the user does enter their password, onlogin fires, then onready. This
> seems in line from the case where the user has been logged into this app
> before.
A simple workaround: ignore onready(). watch() will result in either onlogin() or onlogout() firing, so you can use the first call to either to trigger your onready(). FxA inherited onready() from Persona, and it doesn't map to FxA-on-FxOS meaningfully. You can see how redundant it is here (doReady() ends up firing onready()):
https://github.com/mozilla/gecko-dev/blob/master/toolkit/identity/FirefoxAccounts.jsm#L145
Comment 3•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•