xhr: add new key for ProgressEvent constructor option types
#3137
Conversation
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
github-actions
bot
added
the
feature definition
captainbrosset
approved these changes
Jul 10, 2025
ddbeck
changed the title
xhr: add new keyxhr: add new key for ProgressEvent constructor option types
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.
As far as I can tell, this is a (dubious) "feature" that changes the underlying supported types, which only has the effect of allowing negative JavaScript number values, which were previously forbidden. I think this barely matters, so I folded into the regular XHR feature.
Related:
ProgressEvent()constructor optionsloaded+totalaccept double in Chrome 136 + Firefox 138 mdn/browser-compat-data#26956