Closed
Bug 1030106
Opened 10 years ago
Closed 9 years ago
Standalone UI for link clickers needs "something went wrong" visual and audio notification - GMP plugin crash
Categories
(Hello (Loop) :: Client, defect, P4)
Hello (Loop)
Client
Tracking
(Not tracked)
RESOLVED
INVALID
backlog | - |
People
(Reporter: RT, Unassigned)
References
Details
(Whiteboard: [openh264])
User Story
As a WebRTC browser user in a call, I get notified "something went wrong" if my browser experiences a GMP plugin (OpenH264) crash so that I can dial the other person back and carry on my conversation. (this will apply until the client UI handles call-back URLs on Firefox).
Attachments
(1 file)
288.05 KB,
audio/mpeg
|
Details |
When in a call as a URL clicker on Firefox, my call can terminate because of a desktop problem related to a GMP plugin crash. In that scenario I want to be notified to I can call the other person back and carry on my conversation.
Please note this will only apply until we support URL call-back usage with the client UI.
Reporter | ||
Comment 1•10 years ago
|
||
Initial sound file which may change later.
Reporter | ||
Comment 2•10 years ago
|
||
Please note that as per discussion with Arcadio yesterday we should not be using the "Firefox Hello" brand for now (likely we'll use it when we get to beta). For Nightly and Aurora we should replace "Hello" by "WebRTC" wherever "Hello" appears in the UX and also use the Firefox logo instead of the speech bubble for now.
Updated•10 years ago
|
Target Milestone: mozilla34 → mozilla35
Updated•10 years ago
|
Updated•10 years ago
|
backlog: --- → -
Summary: Standalone UI for link clickers needs "something went wrong" visual and audio notification → Standalone UI for link clickers needs "something went wrong" visual and audio notification - GMP plugin crash
Target Milestone: mozilla35 → ---
Updated•9 years ago
|
Rank: 45
Flags: firefox-backlog+
Priority: P2 → P4
Whiteboard: [openh264]
Reporter | ||
Comment 3•9 years ago
|
||
Marking as invalid since we don't use H264 anymore (was used when in conversations with FFOS users).
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•