Update fetch() browser support in docs #2522
Merged
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
As https://caniuse.com/#feat=fetch shows it's supported since Safari 10.1.
dead-claudia
requested changes
Aug 29, 2019
Co-Authored-By: Isiah Meadows <[email protected]>
dead-claudia
approved these changes
Aug 30, 2019
Merged
StephanHoyer
pushed a commit
that referenced
this pull request
May 16, 2022
* Update fetch() browser support in docs As https://caniuse.com/#feat=fetch shows it's supported since Safari 10.1. * Update docs/request.md Co-Authored-By: Isiah Meadows <[email protected]> [skip ci]
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.
As Can I use shows
fetch()supported since Safari 10.1 and iOS Safari 10.3.Description
Removed Safari from the list of browsers that don't support
fetch().Motivation and Context
This info is outdated.
Other changes to consider (not included in the pull request at the moment):
I don't know: if the first point is still valid or not, as both Fetch and XMLHttpRequest specifications were updated this month. Seems both are subject to specification changes.
The second point seems outdated: it's possible to cancel a request using a AbortController. Browser support is almost the same as
fetch().The third point is still valid: fetch standard still misses upload progress hooks.
About the polyfill size there's this polyfill: 1 kB min, 554 b min+gzip, without AbortController support. According to BundlePhobia, whatwg-fetch is 7.9 kB min and 2.7 kB min+gzip, which raises a question: the "over 11kB" claim is from non-minified code? If so isn't it a bad metric, as it's affected by comments?
Seems the other points, like integration with the autoredrawing subsystem and interpolation, are still valid.
Types of changes
Checklist:
docs/change-log.md