handle invalid utf-16 surrogates on TextDecoder#5673
Merged
Conversation
jasnell
reviewed
Dec 10, 2025
630da30 to
1265301
Compare
CodSpeed Performance ReportMerging #5673 will not alter performanceComparing Summary
Footnotes
|
1265301 to
ae0080e
Compare
jasnell
approved these changes
Dec 12, 2025
ae0080e to
8dee6c3
Compare
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
2 participants
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.
Fixes #5390
Handles invalid utf-16 surrogate pairs and replaces invalid pairs with replacement character if needed. The failing tests are available at https://github.com/web-platform-tests/wpt/blob/master/encoding/textdecoder-utf16-surrogates.any.js