Closed
Bug 978719
Opened 10 years ago
Closed 10 years ago
iceconnectionstate changes from failed to connected
Categories
(Core :: WebRTC: Networking, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 950990
People
(Reporter: thomas, Unassigned)
Details
Attachments
(1 file)
|
7.14 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.117 Safari/537.36 Steps to reproduce: 1. Enter WebRTC service (with TURN servers) in Firefox on restrictive network where connection will fail (without TCP TURN). 2. Enter with Chrome from the same network, or less restrictive network Actual results: iceconnectionstate in Firefox changes in the following order: "new"->"failed"->"connected", and an empty stream is added. iceconnectionstate in Chrome changes in the following order: "new"->"checking", and an empty stream is added. Expected results: The iceconnectionstate in Firefox should have been "failed".
|
Reporter | |
Comment 1•10 years ago
|
||
|
||
Updated•10 years ago
|
Component: WebRTC → WebRTC: Networking
|
||
Comment 2•10 years ago
|
||
This looks like a dupe of 950990. Can you check if it works for you on Aurora or Nightly?
Flags: needinfo?(thomas)
|
|
Reporter | |
Comment 3•10 years ago
|
||
You're right, I can't reproduce it in Nightly.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Flags: needinfo?(thomas)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•