- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Mon, 05 Aug 2024 19:54:05 +0000
- To: public-webrtc@w3.org
jan-ivar has just created a new issue for https://github.com/w3c/webrtc-pc: == Unspecified whether the data channel error event fires from SCTP ABORT == The spec mentions only two sources of ["data-channel-failure"](https://w3c.github.io/webrtc-pc/#dom-rtcerrordetailtype-data-channel-failure): 1. [§ 6.2.6 Error on creating data channels](https://w3c.github.io/webrtc-pc/#error-on-creating-data-channels) 2. [SLD/sRD(answer)](https://w3c.github.io/webrtc-pc/#ref-for-dom-rtcerrordetailtype-data-channel-failure-1): _"If no available ID could be generated, set channel.[[[ReadyState]]](https://w3c.github.io/webrtc-pc/#dfn-readystate) to "[closed](https://w3c.github.io/webrtc-pc/#dom-rtcdatachannelstate-closed)", and add channnel to errorList."_ The first one fires `error` then `close`, the second only `error`. A mistake? But we probably also need § 6.2.8 on what to do with datachannel runtime errors like receiving SCTP ABORT. According to https://wpt.fyi/results/webrtc/RTCDataChannel-close.html both `error` and `close` should fire. We should probably align with implementations here. Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2984 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 5 August 2024 19:54:06 UTC