Closed
Bug 1210501
Opened 9 years ago
Closed 8 years ago
[meta] Improve Hello's handling of disconnected/offline states and error reporting to the user
Categories
(Hello (Loop) :: Client, defect, P3)
Hello (Loop)
Client
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: standard8, Unassigned)
References
Details
Currently we have very little indication to the user if they've been disconnected or if they're offline. As we saw in bug 1207300 we don't handle this at all well.
I think this as a meta bug wants to handle several things:
1) Implement notifications to the user when we a) know the network is offline, b) the network is online but we can't contact the server.
2) Examine our current registration, push handling & notification code for improvements. Currently the backend code sometimes notifies the front-end panel, but not for all events, and additionally the panel code doesn't get/receive notifications of failures from the backend code.
If we decide on the design for 1 first, I think we can use that to work out any revisions we want to our implementation in 2.
Updated•9 years ago
|
Assignee: nobody → b.pmm
Comment 2•9 years ago
|
||
Okay, if I understood it well, is this bug for providing UX for any kind of error or just the two listed above?
Reporter | ||
Comment 3•9 years ago
|
||
(In reply to Pau Masiá [:Pau] from comment #2)
> Okay, if I understood it well, is this bug for providing UX for any kind of
> error or just the two listed above?
Hmm, really we should do the UX work in bug 1210504 and keep this one as the meta for the combined ux & implementation. Hopefully that bug has more information for you about what I'm thinking of.
Assignee: b.pmm → nobody
Updated•9 years ago
|
Rank: 35
Reporter | ||
Comment 6•8 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: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•