- From: docfaraday via GitHub <noreply@w3.org>
- Date: Tue, 02 Jun 2026 16:00:00 +0000
- To: public-webrtc@w3.org
docfaraday has just created a new issue for https://github.com/w3c/webrtc-pc: == RTCPeerConnection.sctp is updated in have-remote-offer, but nothing sets up an RTCDtlsTransport until later, and RTCSctpTransport.transport is not nullable == Spec doesn't create RTCDtlsTransports until have-local-offer or reaching stable via an answer. These are for local descriptions only: https://w3c.github.io/webrtc-pc/#ref-for-dom-rtcdtlstransport-7, https://w3c.github.io/webrtc-pc/#ref-for-dom-rtcdtlstransport-8 This is for answers only: https://w3c.github.io/webrtc-pc/#ref-for-dom-rtcdtlstransport-9 This is for reaching stable (via an answer or I guess rollback) only: https://w3c.github.io/webrtc-pc/#ref-for-dom-rtcdtlstransport-10 wpt.fyi says all browsers leave RTCRtpReceiver/Sender.transport null in have-remote-offer: https://wpt.fyi/results/webrtc/RTCRtpReceiver.https.html?label=master&label=experimental&aligned https://wpt.fyi/results/webrtc/RTCRtpSender.https.html?label=master&label=experimental&aligned Safari and Chrome are setting RTCSctpTransport.transport in have-remote-offer, but RTCSctpTransport.transport.iceTransport.role/component aren't set! (role is null in Chrome and undefined in Safari, component is undefined in both) https://jsfiddle.net/13ufwjxe/ Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3112 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 2 June 2026 16:00:02 UTC