[Webkit-unassigned] [Bug 184688] New: WebRTC DataChannel id of initiator not set

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Apr 17 04:42:14 PDT 2018


https://bugs.webkit.org/show_bug.cgi?id=184688

            Bug ID: 184688
           Summary: WebRTC DataChannel id of initiator not set
           Product: WebKit
           Version: Safari 11
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebRTC
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: db at threema.ch
                CC: youennf at gmail.com

Created attachment 338098

  --> https://bugs.webkit.org/attachment.cgi?id=338098&action=review

Demo

When creating a WebRTC DataChannel with in-band announcement (negotiated=false), the "id" attribute is not set on the side of the initiator.

Demo: https://tmp.dbrgn.ch/dc/

If you open this in Chromium or Firefox, the data channel id will be reported as an integer on both sides.

> DC1 is open. id=1
> DC2 is open. id=3
> New data channel. id=1
> New data channel. id=3

If you open it in Safari 11 or in the current technology preview, it will be reported as null on the initiator side.

> DC1 is open. id=null
> DC2 is open. id=null
> New data channel. id=1
> New data channel. id=3

The JS sourcecode can be found at https://tmp.dbrgn.ch/dc/dc.js.

>From the spec (https://www.w3.org/TR/webrtc/#dom-rtcdatachannel-id):

> The id attribute returns the ID for this RTCDataChannel . The value is initally null, which is what will be returned if the ID was not provided at channel creation time, and the DTLS role of the SCTP transport has not yet been negotiated. Otherwise, it will return the ID that was either selected by the script or generated by the user agent according to [ RTCWEB-DATA-PROTOCOL].

The current behavior seems to be a bug, and it breaks one of our data channel based applications in Safari.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180417/f0c40eca/attachment.html>


More information about the webkit-unassigned mailing list