Repository navigation
fix(fetch): reject NaN and Infinity in JSON request data - #3223
Merged
Pavel Feldman (pavelfeldman) merged 1 commit intoOct 6, 2026
Merged
Conversation
Contributor
|
Pavel Feldman (@pavelfeldman) Thanks for picking this up. This matches the root cause and fix I had reproduced and prepared locally. Glad to see it addressed. |
Yury Semikhatsky (yury-s)
approved these changes
Oct 6, 2026
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
3 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.
Summary
APIRequestContextserialized objectdatawith the defaultjson.dumps, emitting bareNaN/Infinitytokens in anapplication/jsonbody.allow_nan=Falseand raiseErrorinstead, matching the transport fix in fix(transport): reject NaN and Infinity instead of crashing the driver #3221.Fixes microsoft/playwright#43142