[webrtc-pc] Should RTCDataChannel.send be allowed to throw synchronously for not enough buffer space (#3097)

youennf has just created a new issue for https://github.com/w3c/webrtc-pc:

== Should RTCDataChannel.send be allowed to throw synchronously for not enough buffer space ==
As illustrated by https://github.com/web-platform-tests/wpt/issues/58246, Chromium is throwing if hitting a 16MB limit.
On the other hand, Safari is not, which will lead to firing the `error` event and is terminal for that data channel.

With Chromium behaviour, it is easier for web pages to recover as they can know what was not sent and retry later on.
It does seem that, with Chromium's behavior, it should not be possible to hit the internal sctp buffer limit.

So I wonder whether we should tighten the spec and align with Chromium approach here.
We could also define a minimum limit if implementations are aligned there.


Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3097 using your GitHub account


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

Received on Thursday, 12 March 2026 16:12:30 UTC