- From: Philipp Hancke via GitHub <noreply@w3.org>
- Date: Mon, 29 Sep 2025 12:58:23 +0000
- To: public-webrtc-logs@w3.org
https://w3c.github.io/webrtc-pc/#webidl-862292147 also needs a slight tweak, changing > 20. If channel is the first RTCDataChannel created on connection *and no m=section exists for data*, update the negotiation-needed flag for connection. I *think* the condition for that can be expressed using [[SctpTransport]] not being null. Expected behavior: Creating with alwaysNegotiateDataChannels should not fire ONN immediately. Creating with alwaysNegotiateDataChannels and creating a data channel should fire ONN. Creating with alwaysNegotiateDataChannels and adding a audio transceiver should result in two m-lines but fire ONN as result of adding audio. Calling createDataChannel way *after* that should not fire ONN. Drive-by: * Step 19 should check if transport is not null before checkings its connected state? * Step 20 should check if this is the first datachannel on the transport, not the connection or alternatively if a transport needs to be created? SCTP getting rejected and recreated might be rare but... -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/pull/242#issuecomment-3346798662 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 29 September 2025 12:58:24 UTC