Closed
Bug 1067591
Opened 10 years ago
Closed 10 years ago
loop page refresh creates multiple calls / handle 'terminated'/'close' websocket notifications when accepting calls
Categories
(Hello (Loop) :: Client, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: LMS, Unassigned)
References
Details
(Whiteboard: [well filed])
User Story
During connection, if a terminate message with reason "close" is received from the websocket then: - On the standalone side, display the "Call Failed" UI. - On the desktop side, close the window if it is before the user accepted, or put up "Call Failed" if it is after the user accepted.
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:34.0) Gecko/20100101 Firefox/34.0 Build ID: 20140911004004 Steps to reproduce: 1. create a call with someone 2. start call 3. reload page before call loads 4. start call 5. repeat steps 3-4 Actual results: http://i.imgur.com/fTU6fbJ.png Expected results: call should end or should have a pop up saying there's a call in progress to prevent this
Updated•10 years ago
|
Component: WebRTC → Client
Product: Core → Loop
QA Contact: anthony.s.hughes
Version: 34 Branch → unspecified
Comment 2•10 years ago
|
||
Thanks for filing, I think there's various bugs in the process that should help this, e.g. bug 1047410 and bug 1000237 (1000237 is landed but not yet deployed). However, it also gives me a good case for bug 1065974 needing to be fixed, so I'll go and re-open that bug.
Comment 3•10 years ago
|
||
Now bug 1065974 has almost landed, updated the user story with what we need to do to fully resolve this.
User Story: (updated)
Summary: loop page refresh creates multiple calls → loop page refresh creates multiple calls / handle 'terminated'/'close' websocket notifications when accepting calls
Comment 4•10 years ago
|
||
This has been fixed by other bugs.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•