add decodeURIComponent error handling tests for invalid UTF-8 sequences (Fixes #4413) #4414
+87
−0
Conversation
This file contains 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
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.
This PR adds comprehensive test coverage for
decodeURIComponentURIError handling as required by ECMA-262. The tests verify proper error throwing behavior for several types of invalid UTF-8 sequences documented, including:Surrogate pair violations (
%ED%BF%BF)Tests reserved code points (U+D800-DFFF) per
Overlong encodings (
%C0%AF)Verifies rejection of non-minimal-length encodings
Invalid continuation bytes (
%ED%7F%BF)Checks for missing
10xxxxxxcontinuation patternsIncomplete sequences (
%ED%BF)Tests truncated 3-byte sequences
Out-of-range codepoints (
%F4%90%80%80)Validates rejection of codepoints > U+10FFFF
Resolves #4413 by implementing the test case requirements outlined in the issue discussion.