Re: [webrtc-pc] No way to observe DataChannel-only transport events in initial negotiation (#2899)

Looks like we fell behind on writing a PR for this.

Luckily https://jsfiddle.net/jib1/7oupqcm8/56/ shows _all_ browsers already expose `pc.sctp` in `"have-local-offer"`:

Chrome and Safari also expose it in `"have-remote-offer"` and has nullable maxMessageSize as decided:
```
pc1.signalingState = "have-local-offer"
pc1.sctp = { "state": "connecting", "maxMessageSize": null, "maxChannels": null }
pc2.signalingState = "have-remote-offer"
pc2.sctp = { "state": "connecting", "maxMessageSize": null, "maxChannels": null }
pc2.signalingState = "stable"
pc2.sctp = { "state": "connecting", "maxMessageSize": 262144, "maxChannels": null }
pc1.signalingState = "stable"
pc1.sctp = { "state": "connecting", "maxMessageSize": 262144, "maxChannels": null }```
```

Firefox defers `pc2` exposure from `"have-remote-offer"` to `"stable"`, and fakes early maxMessageSize:
```
pc1.signalingState = "have-local-offer"
pc1.sctp = { "state": "connecting", "maxMessageSize": 65536, "maxChannels": null }
pc2.signalingState = "have-remote-offer"
pc2.sctp = null
pc2.signalingState = "stable"
pc2.sctp = { "state": "connecting", "maxMessageSize": 1073741823, "maxChannels": null }
pc1.signalingState = "stable"
pc1.sctp = { "state": "connecting", "maxMessageSize": 1073741823, "maxChannels": null }
pc1.sctp.state = "connected"
```
I'll do a PR based on the former.

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2899#issuecomment-3993742374 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 3 March 2026 21:47:05 UTC