Open Bug 1513107 Opened 7 years ago Updated 3 years ago

ondatachannel event will usually not fire for channel created after closing another channel

Categories

(Core :: WebRTC: Networking, defect, P3)

Product:
Core
Component:
WebRTC: Networking
Version:
63 Branch
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox64 --- affected
firefox65 --- affected
firefox66 --- affected

People

(Reporter: thomasmullendesign, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.80 Safari/537.36 Steps to reproduce: The ondatachannel event will not fire for data channels created after another datachannel was closed. 1) Create a datachannel. 2) Close the datachannel, then create a new one. 3) Observe that the datachannel OPENS but it not announced in any way to the remote peer. The datachannel event does not fire, the channel's readyState changes to "open". Chrome displays the correct behaviour. Simple, minimal reproduction: https://codepen.io/RationalCoding/pen/KbwZEz?editors=0011 Actual results: The datachannel event does not fire. Expected results: The datachannel event should fire.
The issue happens most (~90%) of the time. Occasionally it will work as intended.
Reproducible on Firefox Nightly 66.0a1 (2018-12-13), Firefox 65.0b4 and Firefox 64 on Windows 10 x64, Windows 7 x32, Ubuntu 16.04 and Mac OS X 10.13.
Status: UNCONFIRMED → NEW
status-firefox64: --- → affected
status-firefox65: --- → affected
status-firefox66: --- → affected
Component: Untriaged → WebRTC: Networking
Ever confirmed: true
Product: Firefox → Core
Byron, could you help me triage this?
Flags: needinfo?(docfaraday)
Rank: 25
Flags: needinfo?(docfaraday)
Priority: -- → P3

Any update on this? It's not possible to do multiplexed data channels on Firefox with this bug.

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.