Closed
Bug 1101131
Opened 11 years ago
Closed 8 years ago
Disable navigator.mozId.logout() for RPs once they have called watch() with FxAccounts
Categories
(Firefox OS Graveyard :: FxA, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: spenrose, Unassigned)
Details
navigator.mozId.logout() is properly exposed for use with Persona. It should not be used with Firefox Accounts, which has a single state on device controlled via the Settings UX and Gecko state, not RP prompts. Once an RP has passed {wantIssuer: 'firefox-accounts'} to watch(), B2G should not allow logout() to sign the user out of FxA on device.
Comment 1•11 years ago
|
||
Ah, the joys of reusing an unversioned API with totally different semantics :-P
Any RPs that support FxOS < 2.2 will still need to avoid calling mozId.logout(), since it's way too late to backport this fix.
| Reporter | ||
Comment 2•11 years ago
|
||
(In reply to Jared Hirsch [:_6a68] [NEEDINFO pls] from comment #1)
> Ah, the joys of reusing an unversioned API with totally different semantics
> :-P
>
> Any RPs that support FxOS < 2.2 will still need to avoid calling
> mozId.logout(), since it's way too late to backport this fix.
I don't think it's that bad. No 2.0- or 2.1-bundled RP code should land that invokes logout(). Later code that targets those versions we should be able to intercept or update.
Comment 3•11 years ago
|
||
All docs need to be updated in the event that logout should not be called.
| Reporter | ||
Updated•11 years ago
|
Assignee: spenrose → nobody
Comment 4•8 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•