Closed
Bug 936487
Opened 11 years ago
Closed 11 years ago
A way to enable/disable Firefox Accounts on FirefoxOS
Categories
(Core Graveyard :: Identity, defect)
Core Graveyard
Identity
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 929386
People
(Reporter: jedp, Assigned: jedp)
References
Details
(Whiteboard: [qa+])
In case we have to switch this thing off in a hurry, we need a way to enable and disable Firefox Accounts in FirefoxOS both in gecko and in gaia.
The current thinking is that we will have a pref in gecko, and a build-time parameter for gaia.
Note that we will need a pref anyway for the firefox accounts url, just as we do for persona, to enable us to use different backend services for testing.
(It would be possible to have a setting in gaia triggered by the gecko pref, but this would require modifications to the settings database, which we would prefer not to make.)
Updated•11 years ago
|
Whiteboard: [qa+]
Comment 1•11 years ago
|
||
If we get past November 22, we'll need to make sure that switch on/off code is also in Marketplace and WMF. LMK if that calls for a separate bug.
Comment 2•11 years ago
|
||
Jed, can we change the status on this one?
Assignee | ||
Comment 3•11 years ago
|
||
Yes, this is implemented in the patches in Bug 929386.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 4•11 years ago
|
||
Nice.
Can one of you add details here on how FxA would be enabled/disabled on the phone?
Would this still require a code change and build that would become a dot release to a phone, for example?
Or we this be an "on the phone" pref setting?
Comment 5•11 years ago
|
||
Please either dupe this to bug 929386 or wait until it lands on m-c before marking it FIXED.
Assignee | ||
Comment 6•11 years ago
|
||
It's not possible to have a pref to disable the UI on the phone. Gaia can't access prefs; but furthermore, the inclusion of all the UI (Settings, FTU, etc.) is happening at build time. So there would have to be a build config to exclude FXA from the phone.
Since FXA is committed to b2g 1.4, I don't think we need a way to disable on the device. It's not appearing in the 1.3 codebase, and so b2g builds with FXA would be deliberate anyway. But for nightly firefox, while we sort out the FXA features, we do need a gecko pref. That's what's provided in Bug 929386.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → DUPLICATE
Comment 7•11 years ago
|
||
OK. We are going the dupe route. Verified as such.
Status: RESOLVED → VERIFIED
Updated•6 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•