This UX is for outgoing call failures (to contacts). The UX implementation is already tracked under https://bugzilla.mozilla.org/show_bug.cgi?id=1000186 Or am I misunderstanding this bug?

(In reply to Romain Testard [:RT - on PTO back on August 14th] from comment #1) > This UX is for outgoing call failures (to contacts). > The UX implementation is already tracked under > https://bugzilla.mozilla.org/show_bug.cgi?id=1000186 > > Or am I misunderstanding this bug? We've just been discussing this with Darrin - we need a call failed indication for the hopefully rare cases where the incoming call fails to set-up correctly. Hence, although the mock-up is intended for outgoing, using it (without most of the buttons) for incoming is is also fine.

So, does this cover the "Cancel button" and "E-mail link" from https://bugzilla.mozilla.org/show_bug.cgi?id=1000186#c7 ?

(In reply to Paul Silaghi, QA [:pauly] from comment #3) > So, does this cover the "Cancel button" and "E-mail link" from > https://bugzilla.mozilla.org/show_bug.cgi?id=1000186#c7 ? I'm not expecting it to currently, I think lets file new bugs to be safe.

Darrin -- Does this require any new strings or would we reuse strings from other views?

I think the strings in https://people.mozilla.org/~dhenein/labs/loop-mvp-spec/#link-prompt should be fine, unless someone had needinfo'd matej for alternate copy elsewhere.

What would the cancel button do in this case?

Also would the email button generate a new URL to send?

Hmm, this is part of the desktop direct calling case. We can't do this until we have the start of direct calling on desktop.

(In reply to Mark Banner (:standard8) from comment #9) > Hmm, this is part of the desktop direct calling case. We can't do this until > we have the start of direct calling on desktop. So having another look at the bugs, it is actually a bit unclear. I am therefore going to make the decision that this bug is for implementing the view. Just display the appropriate generic failure text. I'll file new bugs to cover adding the buttons later.

Is there a way to simulate a call failure so this can be tested?

I just talked to Darrin and given that this is only going to happen in the case where the Desktop user is called back, it makes sense to display "Something went wrong" (instead of "Call Failed") -- and to not show the "Retry" or "Email" buttons. At most we'd show the "cancel" button (if that didn't look odd).

I think this bug should include adding the "cancel" button (again, assuming the "cancel" button by itself doesn't look odd).

WIP patch that is almost ready, just needs tests writing.

This fixes the tests as well. Although we could try and share the view with the flux implementation of the call failed for outgoing calls, this seems a bit difficult at the moment - they are based on different ideas, and the outgoing one is tied to flux. Hence I'm thinking we should leave sharing the view until we fluxify the incoming call code. The best way to test this at the moment is to start an incoming call from a url, but not accept audio/video media on the caller's side after the call is accepted. Then just let it time out.

Comment on attachment 8511028 [details] [diff] [review] Desktop client should display Call Failed if an incoming call fails during set-up Review of attachment 8511028 [details] [diff] [review]: ----------------------------------------------------------------- LGTM, r=me with the nit addressed. ::: browser/components/loop/content/js/conversation.jsx @@ +181,5 @@ > /** > + * Incoming Call failed view. Displayed when a call fails. > + * > + * XXX Based on CallFailedView, but built specially until we flux-ify the > + * incoming call views. Nit: Please add the bug number as a reference.

https://hg.mozilla.org/integration/fx-team/rev/705cec97abf1 For test steps, see comment 16.

Comment on attachment 8511028 [details] [diff] [review] Desktop client should display Call Failed if an incoming call fails during set-up Approval Request Comment [Feature/regressing bug #]:Displaying call failed to user [User impact if declined]: the user would see a feedback form for a call that was not successfully completed [Describe test coverage new/current, TBPL]: unit tests, manually verified [Risks and why]: No risk outside of Hello; low risk to Hello; without this, users who couldn't connect would see a feedback form for a call that didn't happen -- which would be confusing and could skew user metrics (which product is depending on) [String/UUID change made/needed]: No strings

(In reply to Wes Kocher (:KWierso) from comment #20) > https://hg.mozilla.org/mozilla-central/rev/705cec97abf1 Paul, can you please confirm this is fixed in the latest Nightly?

Tested on Nightly 10/25; looks good.

Comment on attachment 8511028 [details] [diff] [review] Desktop client should display Call Failed if an incoming call fails during set-up Aurora+ The plan is to verify on Aurora on Sunday before uplift for beta4.

Verified on Aurora Nightly 10/26 Linux

Comment on attachment 8511028 [details] [diff] [review] Desktop client should display Call Failed if an incoming call fails during set-up Beta+

(In reply to Maire Reavy [:mreavy] (Plz needinfo me) from comment #13) > I just talked to Darrin and given that this is only going to happen in the > case where the Desktop user is called back, it makes sense to display > "Something went wrong" (instead of "Call Failed") -- and to not show the > "Retry" or "Email" buttons. At most we'd show the "cancel" button (if that > didn't look odd). "Something went wrong" and "Cancel" button displayed for guest users. Verified fixed FF 34b4.