Status

Hello (Loop)
Client
P3
normal
RESOLVED WORKSFORME
4 years ago
3 years ago

People

(Reporter: tomasz, Unassigned)

Tracking

unspecified
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [investigation])

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Created attachment 8518480 [details]
many-errors.png

There was some issue with the network and I got 3 errors about it. What makes it worse is that the last error shows up with the delay and so when I open the window it show the errors and the a new error shows-up and it looks like a super-warning that Firefox is about to disintegrate.
Sevaan, can you look at this from a UX perspective?
Flags: needinfo?(sfranks)
A solution to explore here may be to prioritize them. For example, "Service unavailable" would probably trump "Unable to retrieve call URL".

RT, Can you provide a list of all the error messages currently available in Hello (or refer me to someone who can)?
Flags: needinfo?(sfranks) → needinfo?(rtestard)

Comment 3

4 years ago
Hi Matej, can you please point us to the list of error messages?
Flags: needinfo?(rtestard) → needinfo?(Mnovak)

Comment 4

4 years ago
(In reply to Romain Testard [:RT] from comment #3)
> Hi Matej, can you please point us to the list of error messages?

Sorry, I don't have that list. Not sure who to point you to, but maybe Darrin or Shell?
Flags: needinfo?(Mnovak)

Comment 5

4 years ago
Maire is going to work on a list of all our client error messages for Sevaan and the error codes that come from the platform/backend.

work with Shell and Sevaan on a public list and prioritize what to display to user.
Flags: needinfo?(sescalante)
Flags: needinfo?(mreavy)

Updated

4 years ago
backlog: --- → Fx37+
Flags: needinfo?(sescalante)
Priority: -- → P1
Shell, Can I ask you to add this to what we want to do in Portland?  Basically, 
(1) pull together the list from the documentation we have, 
(2) identify any holes in the document, 
(3) identify a couple of people to fill those holes, 
(4) update the documentation and give it to Sevaan so he has what he needs to consolidate the error messages?
Flags: needinfo?(mreavy)

Comment 7

4 years ago
map out all our errors - ping maire as needed.
Flags: needinfo?(sescalante)
Priority: P1 → P2
There's "homework" needed to finish out the user story for this and provide something actionable for a developer.  So I'm moving this to Fx38? since this homework won't happen until January
backlog: Fx37+ → Fx38?

Comment 9

3 years ago
find if still an issue - timebox.  find how to repro
backlog: Fx38? → Fx39+
Flags: needinfo?(sescalante)
Priority: P2 → P3

Comment 10

3 years ago
calls are being drastically redesigned, including error handling like rooms.  if we see these errors again after the re-design will put someone on it to investigate.
backlog: Fx39+ → backlog-
Whiteboard: [investigation]
Since we've moved to the rooms model, we no longer get these kind of errors being stacked. Therefore closing this as WFM.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.