Closed
Bug 1203138
Opened 10 years ago
Closed 10 years ago
The user should be notified if the connection to the push server is down for long periods
Categories
(Hello (Loop) :: Client, defect, P2)
Hello (Loop)
Client
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1210501
People
(Reporter: standard8, Unassigned)
References
Details
Trying to combine a couple of similar bugs (bug 1070230, bug 1092361) into one here.
Loop relies on a connection to a push server to receive notifications of incoming calls and room joins. If that connection to the push server goes down, we have a mechanism to automatically retry the connection. Firstly after a minute, then 2, then 3, going up to every 5 minutes.
Currently, whilst that connection is down, the user doesn't get notified at all. Hence they may be expecting a notification, but they don't get it, nor do they see a reason for missing it.
We should probably do something like:
- Notify the user in the panel after 'x' period
- (possibly) notify the user via the toolbar icon after 'x' period
I'm not sure we need an active alert, but at least a passive one so that they're made aware of it.
Sevaan: I'm looking for UX input here as to what we should do.
Flags: needinfo?(sfranks)
Comment 3•10 years ago
|
||
Let's display a message in the panel à la this design: http://i.sevaan.com/image/3I2t1J2v2N2F
And the toolbar icon should turn red after the third connection attempt.
Updated•10 years ago
|
Flags: needinfo?(sfranks)
Reporter | ||
Updated•10 years ago
|
Points: --- → 5
Rank: 26
Flags: qe-verify+
Flags: firefox-backlog+
Priority: -- → P2
Reporter | ||
Comment 4•10 years ago
|
||
We're now going to be handling this in bug 1210501 (and I'd unfortunately forgotten about this bug).
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•