Skip to content

safari: don't shim maxMessageSize when RTCSctpTransport is native - #1201

Merged
fippo merged 1 commit into
mainfrom
sctp-gate
Sep 7, 2026
Merged

fippo merged 1 commit into
mainfrom
sctp-gate

Conversation

@fippo

@fippo fippo commented Sep 7, 2026

Copy link
Copy Markdown
Member

Unlike Chrome and Firefox, Safari has no gate in shimMaxMessageSize, so the setRemoteDescription wrapper is installed unconditionally. When pc.sctp is native the getter it feeds is not installed, which means the value parsed out of every remote description can not be read by anyone -- and it disagrees with what apps actually see (65536 vs the native 262144 in WebKit 26).

Gate on the presence of the attribute rather than a version so old Safari keeps the shim.

Unlike Chrome and Firefox, Safari has no gate in shimMaxMessageSize, so the
setRemoteDescription wrapper is installed unconditionally. When pc.sctp is
native the getter it feeds is not installed, which means the value parsed out
of every remote description can not be read by anyone -- and it disagrees with
what apps actually see (65536 vs the native 262144 in WebKit 26).

Gate on the presence of the attribute rather than a version so old Safari
keeps the shim.
@fippo
fippo merged commit 34c4b2a into main Sep 7, 2026
8 checks passed
@fippo
fippo deleted the sctp-gate branch September 7, 2026 06:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant