Closed
Bug 993794
Opened 11 years ago
Closed 11 years ago
FxA Settings app: Remove code that checks if FxA is preffed off
Categories
(Firefox OS Graveyard :: FxA, defect, P2)
Tracking
(b2g-v2.0 fixed)
RESOLVED
FIXED
2.0 S3 (6june)
Tracking | Status | |
---|---|---|
b2g-v2.0 | --- | fixed |
People
(Reporter: jhirsch, Assigned: jhirsch)
References
Details
(Whiteboard: [fxa4fxos2.0][qa+])
Attachments
(1 file)
Same thing as bug 983452 - since firefox accounts is shipping in 1.5, let's pull out the unneeded code which checks if it's disabled.
Assignee | ||
Updated•11 years ago
|
Assignee | ||
Comment 1•11 years ago
|
||
per discussion in bug 967783, maybe we want to promote this to blocker?
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → 6a68
Priority: -- → P2
Updated•11 years ago
|
OS: Mac OS X → Gonk (Firefox OS)
Hardware: x86 → All
Whiteboard: [fxa4fxos2.0]
Assignee | ||
Comment 3•11 years ago
|
||
I was incorrect in c1: bug 996476 is the bug that discusses problems with OTA updates and this pref.
Assignee | ||
Comment 4•11 years ago
|
||
Hi Arthur and Francisco,
Do you guys have time for a small review? This patch removes the pref that disabled FxA, plus code that looks for that pref.
More details:
We preffed off FxA for the 1.4 release, and when it was preffed on, it turned out that OTA updates didn't catch the pref change (bug 996476). Since we don't plan to disable FxA again, the best solution seems to be removing the code that checks for the pref.
FTU and Settings are separately impacted, but if I remove (say) the FTU pref-checking code and delete the pref, then the Settings marionette test will fail. Rather than 3 PRs (one for FTU, one for Settings, one to finally remove the pref), I'm opting for one PR with multiple reviewers.
We're getting a bit close to the wire, so if you're too busy to take this review, please let me know who would be a good alternate, and I'll r? them instead.
Thank you!
Jared
Attachment #8427826 -
Flags: review?(francisco.jordano)
Attachment #8427826 -
Flags: review?(arthur.chen)
Comment 5•11 years ago
|
||
Comment on attachment 8427826 [details]
Github PR 19507
r=me for the settings part, thanks.
Attachment #8427826 -
Flags: review?(arthur.chen) → review+
Comment 6•11 years ago
|
||
Comment on attachment 8427826 [details]
Github PR 19507
FTU part looking good to me.
One thing, this is just curiosity, was thinking about dead settings keys. From people upgrading from 1.4 -> 1.5 we will be leaving that key. Not that is an important thing since we don't use the key, but was just figuring out if we have a global mechanism to remove those dead keys.
Cheers,
F.
Attachment #8427826 -
Flags: review?(francisco) → review+
Assignee | ||
Comment 7•11 years ago
|
||
Thanks for the reviews, guys!
(In reply to Francisco Jordano [:arcturus] [:francisco] from comment #6)
> One thing, this is just curiosity, was thinking about dead settings keys.
> From people upgrading from 1.4 -> 1.5 we will be leaving that key. Not that
> is an important thing since we don't use the key, but was just figuring out
> if we have a global mechanism to remove those dead keys.
Great question. I've seen a lot of bugs related to FOTA problems, but I haven't found a canonical bug related to updates of global settings.
Assignee | ||
Comment 8•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
status-b2g-v2.0:
--- → fixed
Resolution: --- → FIXED
Whiteboard: [fxa4fxos2.0] → [fxa4fxos2.0][qa+]
Target Milestone: --- → 2.0 S3 (6june)
You need to log in
before you can comment on or make changes to this bug.
Description
•