Revise fetch-request-streams compat keys and description#4055
Merged
Conversation
This builds on web-platform-dx#3361 Co-authored-by: jgraham <294864+jgraham@users.noreply.github.com>
github-actions
Bot
added
the
feature definition
captainbrosset
approved these changes
May 19, 2026
Collaborator
Author
|
@jgraham I am going to go ahead with merging this. If you have further feedback on the fetch family of features, please open a new issue or PR. Thank you! |
ddbeck
deleted the
revise-fetch-request-streams-compat-keys-and-description/rmxqokopntxq
branch
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.
This PR assigns keys (one formerly in fetch, one new) to
fetch-request-streamsto more accurately reflect its support in browsers. It also rewrites the description, to more clearly describe the entrypoint into this feature.This builds on and closes #3361. I've added @jgraham as a coauthor to my commit, to reflect his initial work on this problem.
See #3361 (comment) and mdn/browser-compat-data#29451 for some more background on how this data came to be.