Desktop client needs "something went wrong" visual and audio notification in direct calling scenarios - for GMP plugins

RESOLVED INVALID

Status

Hello (Loop)
Client
P4
enhancement
Rank:
45
RESOLVED INVALID
4 years ago
3 years ago

People

(Reporter: RT, Unassigned)

Tracking

unspecified
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [openh264])

User Story

As a signed-in FF browser user in a call, I get notified "something went wrong" if my browser experiences a GMP plugin (OpenH264) crash so that I can call the other peer back.

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
When in a call, 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.
(Reporter)

Comment 1

4 years ago
Darrin, this is a new request for a UI allowing users to be notified when an error occurs during an ongoing call and then re-dial if possible (i.e not possible if the call originated from a link clicker).
Flags: needinfo?(dhenein)
(Reporter)

Updated

4 years ago
Depends on: 1009764
(Reporter)

Updated

4 years ago
Depends on: 1030097
(Reporter)

Updated

4 years ago
No longer depends on: 1009764
I propose we use a variant of https://people.mozilla.org/~dhenein/labs/loop-mvp-spec/#call-ended or https://people.mozilla.org/~dhenein/labs/loop-mvp-spec/#link-prompt with a different title ('Call Failed'?) and the appropriate buttons ('Close' and 'Call Back' if possible)
Flags: needinfo?(dhenein)
(Reporter)

Comment 3

4 years ago
I think we need to break down the scenarios:
=> The user is registered and was on a direct call - when the bug occurs the user is offered to call the other person back through the UI (this bug)
=> The user is on a call with a link clicker - addressed now in bug 1035289

So in this scenario a variant of https://people.mozilla.org/~dhenein/labs/loop-mvp-spec/#call-ended applies so that the registered user can call the other registered peer back.
User Story: (updated)
Summary: Desktop client needs "something went wrong" visual and audio notification → Desktop client needs "something went wrong" visual and audio notification in direct calling scenarios
(Reporter)

Comment 4

4 years ago
Created attachment 8458618 [details]
Call Failed.mp3

Initial sound file which may change later.

Comment 5

4 years ago
requires Fxa
Priority: P2 → --
Whiteboard: [fxa]
Target Milestone: mozilla34 → mozilla35
Priority: -- → P3
not needed for the first release of FxA & contacts
Blocks: 1030097
No longer depends on: 1030097
Blocks: 1066017
No longer blocks: 1000788
Severity: normal → enhancement
backlog: --- → -
Summary: Desktop client needs "something went wrong" visual and audio notification in direct calling scenarios → Desktop client needs "something went wrong" visual and audio notification in direct calling scenarios - for GMP plugins
Target Milestone: mozilla35 → ---

Updated

4 years ago
Priority: P3 → P5
backlog: - → backlog

Updated

4 years ago
backlog: backlog+ → backlog-

Comment 7

3 years ago
not using openh264 by default at the moment... that is the fall back mainly for phones.  desktop is vp8

may hit with android....?
Rank: 45
Priority: P5 → P4
Whiteboard: [fxa] → [openh264]
Whiteboard: [openh264] → [openh264][triage]
Hello no longer has direct calling, so this bug no longer applies
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INVALID
Whiteboard: [openh264][triage] → [openh264]
You need to log in before you can comment on or make changes to this bug.