Open Bug 996494 Opened 10 years ago Updated 4 months ago

Implement nsIFxAccountsUIGlue in desktop

Categories

(Firefox :: Firefox Accounts, enhancement)

enhancement
Points:
8

Tracking

()

People

(Reporter: ferjm, Unassigned)

Details

Consumers of the FxAccounts API shouldn't need to manage account states. In B2G, when a consumer asks for an assertion and there is no logged-in account, we automatically launch the login UI. If the login is successful (and the account used is verified), the consumer gets the assertion.

It would be great to have this same experience in desktop. This way, consumers like the Loop client should need to worry about opening about:accounts or asking the user to do it or even check if there is an existing account. It should only need to call FxAccounts.getAssertion().

We can do it by implementing nsIFxAccountsUIGlue [1] in desktop and moving part of this logic from FxAccountsManager [2] to FxAccounts [3]. We can also make it optional, so the consumer can decide if it wants the platform to trigger the login UI or not.

We can start with the singInFlow [4] only.

[1] https://mxr.mozilla.org/mozilla-central/source/services/fxaccounts/interfaces/nsIFxAccountsUIGlue.idl
[2] https://mxr.mozilla.org/mozilla-central/source/services/fxaccounts/FxAccountsManager.jsm#412
[3] https://mxr.mozilla.org/mozilla-central/source/services/fxaccounts/FxAccounts.jsm#409
[4] https://mxr.mozilla.org/mozilla-central/source/services/fxaccounts/interfaces/nsIFxAccountsUIGlue.idl#11
Component: Client → FxAccounts
Product: Loop → Core
(In reply to Fernando Jiménez Moreno [:ferjm] from comment #0)
> This way,
> consumers like the Loop client should need to worry about opening
> about:accounts

s/should/should NOT/
Flags: needinfo?(mhammond)
Flags: needinfo?(mhammond)
Mark, do you think this is worth trying?
Flags: needinfo?(mhammond)
If loop becomes the first FxA desktop consumer that isn't Sync, then yeah, we should do this.
Flags: needinfo?(mhammond)
No longer blocks: 979845
Blocks: 979845
Priority: -- → P2
Whiteboard: p=?
Target Milestone: --- → mozilla33
Flags: firefox-backlog+
Priority: P2 → P1
Target Milestone: mozilla33 → mozilla34
Points: --- → 8
Whiteboard: p=?
Marco, please remove this from the prioritized backlog as ckarlof tells me there are no current plans to implement this. We are going with bug 1022064 for now instead.
Flags: needinfo?(mmucci)
Target Milestone: mozilla34 → ---
Removed from Iteration 33.3 prioritized backlog.
Flags: needinfo?(mmucci)
No longer blocks: 979845
This doesn't block FxA/Loop integration, as mentioned by :mattN in comment 4.
Flags: firefox-backlog+
Priority: P1 → P3
Severity: normal → enhancement
Priority: P3 → --
Product: Core → Firefox
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.