chrome: don't polyfill .sctp and max-message-size - #1187
Merged
Conversation
fippo
force-pushed
the
guard-maxmessagesize
branch
from
April 20, 2026 19:33
cfffb86 to
3ed3538
Compare
Member
Author
|
The test is actually correct (surprise) and Firefox needs a little more work: |
fippo
changed the title
fippo
force-pushed
the
guard-maxmessagesize
branch
3 times, most recently
from
April 21, 2026 05:05
6323078 to
d60f43c
Compare
in Chrome 102+ with only unified plan Note: the polyfill set pc.sctp after SRD, not after a complete offer/answer cycle.
fippo
force-pushed
the
guard-maxmessagesize
branch
from
April 21, 2026 05:27
d60f43c to
8e3d2eb
Compare
Member
Author
|
Interesting, native Chrome rejects 2GB max-message size while Firefox accepts it: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
in Chrome 102+ with only unified plan
See #1182