Closed Bug 1124360 Opened 5 years ago Closed 5 years ago
direct calls that are rejected through the chatbox close button show "Something went wrong" to the caller rather than "caller unavailable"
Technical checklist: * move clearCallInProgress from conversation.jsx window 'unload' handler to both of: ** conversationStore.js (for outgoing call) *** SharedActions.windowUnload should call hangup (need to register a windowUnload method and register with the conversationStore for that action) ** incoming call code *** "IncomingConversationView#endCall" should call hangup
When the callee clicks X in the incoming call window, the caller gets a message saying "something went wrong" when really the callee has requested that they are unavailable.
5 years ago
This has been fixed by the work on bug 1088672 - the rewrite included hooking up window unload and doing the right thing in the close-whilst-alerting state.
Assignee: nobody → standard8
Status: NEW → RESOLVED
Iteration: --- → 39.1 - 9 Mar
Closed: 5 years ago
Depends on: 1088672
Resolution: --- → FIXED
Whiteboard: [fixed by bug 1088672]
Target Milestone: --- → mozilla39
You need to log in before you can comment on or make changes to this bug.