1441723 - readyState after createDataChannel() should always be "connecting".

Status: NEW

(Core :: WebRTC, defect, P2)

Description

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

The spec [1] says the initial state of a data channel is always "connecting". Specifically:

    const dc = pc.createDataChannel("dc");
    console.log(dc.readyState);             // "connecting"

Firefox (and Chrome btw) get it wrong for subsequent data channels of an established peer connection:

    const dc = pc.createDataChannel("dc");
    console.log(dc.readyState);                   // "open"
    dc.onopen = () => console.log(dc.readyState); // "open"

Strangely, you can register an onopen callback in open state and it still fires!

The spec [2] says readyState is only set to "open" in the queued task that fires the `onopen` event.

STR:
 1. Open https://jsfiddle.net/jib1/uewthp80/

Expected result:

dc3 connecting
dc3 onopen open

Actual result:

dc3 open
dc3 onopen open

AFAIK this is not a regression.

[1] http://w3c.github.io/webrtc-pc/#dom-peerconnection-createdatachannel
[2] http://w3c.github.io/webrtc-pc/#announce-datachannel-open

Comment 1

[Lennart Grahl [:lgrahl]]

Will write a WPT test for this.