Closed
Bug 1076377
Opened 11 years ago
Closed 9 years ago
Differentiate between a login expiring and the inability to login in error messages for a 401
Categories
(Hello (Loop) :: Client, enhancement, P4)
Hello (Loop)
Client
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
| backlog | backlog+ |
People
(Reporter: MattN, Unassigned)
References
Details
(Whiteboard: [strings-added already][errors])
We have two strings that manifest themselves in the same way (HTTP 401) on the server but happen at different times in a user's usage of the feature:
> could_not_authenticate=Could Not Authenticate
> login_expired=Your Login Has Expired
For bug 1047164 I'm just using could_not_authenticate for both cases since it's more general and somewhat covers both cases.
We should either:
* make the code smarter to know if the error happened as a result of the user initiating a new login (not after a restart) vs. the session expiring
OR
* consolidate into one string since login_expired is unused.
Flags: qe-verify+
Flags: firefox-backlog+
|
Reporter | |
Updated•11 years ago
|
Priority: -- → P4
|
||
Updated•11 years ago
|
backlog: --- → Fx36?
|
|
||
Updated•11 years ago
|
backlog: Fx36? → Fx37?
Whiteboard: [strings]
|
|
Reporter | |
Comment 1•11 years ago
|
||
The strings are already in the product so this probably doesn't need [strings] in the whiteboard.
|
|
||
Updated•11 years ago
|
backlog: Fx37? → Fx38?
Whiteboard: [strings] → [strings-added already]
|
|
||
Updated•11 years ago
|
backlog: Fx38? → backlog+
Rank: 46
Whiteboard: [strings-added already] → [strings-added already][errors]
|
||
Comment 2•9 years ago
|
||
Support for Hello/Loop has been discontinued.
https://support.mozilla.org/kb/hello-status
Hence closing the old bugs. Thank you for your support.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•