Closed
Bug 1004999
Opened 11 years ago
Closed 9 years ago
MozLoopService should handle offline mode
Categories
(Hello (Loop) :: Client, defect, P4)
Hello (Loop)
Client
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1210501
| backlog | - |
People
(Reporter: standard8, Unassigned)
References
Details
(Whiteboard: [visibility])
MozLoopService should handle offline mode in the browser - putting up correct notifications etc.
|
Reporter | |
Updated•10 years ago
|
Priority: -- → P3
Target Milestone: --- → mozilla34
|
||
Comment 1•10 years ago
|
||
moving to fx35 - this is just more graceful handling than a general error. good contributor bug
Whiteboard: [visibility]
Target Milestone: mozilla34 → mozilla35
|
||
Comment 2•10 years ago
|
||
Wouldn't we need a design for this? Or just disable the Loop call button?
Flags: needinfo?(standard8)
|
||
Comment 3•10 years ago
|
||
How is this different from bug 1002416?
|
|
Reporter | |
Comment 4•10 years ago
|
||
This probably isn't significantly different from bug 1002416?. I think what's best to do is to finish implementing bug 1002416, then take another look at this bug when the browser is in offline mode, and determine if we're happy with the result or not.
Depends on: 1002416
Flags: needinfo?(standard8)
|
||
Updated•10 years ago
|
backlog: --- → Fx38?
Target Milestone: mozilla35 → ---
|
|
||
Updated•10 years ago
|
backlog: Fx38? → -
|
|
||
Updated•10 years ago
|
Rank: 46
Flags: firefox-backlog+
Priority: P3 → P4
|
|
Reporter | |
Comment 5•9 years ago
|
||
Its not clear at the moment that this is the "thing" we still need to do to make our UX work better. We've now got a new meta bug for dealing with offline/disconnections, so I'm going to close this one, and once we work out what we want to do, then we can file bugs appropriately.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•