Closed
Bug 951495
Opened 10 years ago
Closed 9 years ago
Implement bug-out option in Desktop native Firefox Account UI
Categories
(Cloud Services :: Server: Firefox Accounts, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: ckarlof, Unassigned)
References
Details
(Whiteboard: [qa+])
Similar to bug 951306, Desktop Firefox needs to support error handling of situations when it detects it's a legacy client. Relevant server issues: https://github.com/mozilla/fxa-auth-server/issues/452 https://github.com/mozilla/fxa-auth-server/issues/451 https://github.com/mozilla/fxa-auth-server/issues/449
Updated•10 years ago
|
Whiteboard: [qa+]
Updated•10 years ago
|
Assignee: rfkelly → nobody
Reporter | ||
Comment 1•10 years ago
|
||
For Fx29, we could wire this errors to the "invalid authentication" state, which would trigger the user to log back in, and better error handling could happen in the hosted page in about:accounts.
Comment 2•10 years ago
|
||
We don't actually need to get this in 29 since we're reasonably confident that 29 won't ever be a "legacy client", right?
Reporter | ||
Comment 3•10 years ago
|
||
(In reply to :Gavin Sharp (email gavin@gavinsharp.com) from comment #2) > We don't actually need to get this in 29 since we're reasonably confident > that 29 won't ever be a "legacy client", right? Of course it will! Everything changes (or goes away). It would nice to get this in Fx29, but if we don't that means that future users of Fx29 could potentially have confusing error messages.
Comment 4•10 years ago
|
||
(In reply to Chris Karlof [:ckarlof] from comment #3) > (In reply to :Gavin Sharp (email gavin@gavinsharp.com) from comment #2) > > We don't actually need to get this in 29 since we're reasonably confident > > that 29 won't ever be a "legacy client", right? > > Of course it will! Everything changes (or goes away). It would nice to get > this in Fx29, but if we don't that means that future users of Fx29 could > potentially have confusing error messages. I misspoke. Sure, it will eventually be a legacy client, but not before we ship Firefox 30 (or 45). Given our update rates, we don't have any expectation that a significant number of users will be stuck on 29 when we eventually make it a "legacy client", so it doesn't strictly need to handle that scenario, and I am pushing back on it having anything it doesn't strictly need :)
No longer blocks: 969593
Comment 5•9 years ago
|
||
I think this bug is old enough and under-specified enough that we should just close it out and revisit in a more specific bug if we feel like there's more work to do on this flow.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•