Updating Safari support for HTTP3 - #7200
Merged
Merged
Conversation
As of Sept 2024, Safari 16+ supports HTTP3 for all users. Previously, a subset of users had support enabled (as long as they had Safari 14 or later (including Big Sur or later for Safari on macOS). There was a feature flag available in Safari 14.0-16.3 that allowed users to force HTTP3 on (it was removed for Safari 16.4+). Unlike other feature flags, having the flag off did not disable HTTP3, it just meant maybe the user got it, maybe they didn't. It's complex to communicate all this in a dataset that assumes features ship with a new version of the browser. In this case, the changes are on being made elsewhere, and are not dependent on updating the browser.
Contributor
Author
|
Resolves #7114 |
Owner
|
Thanks! Yeah I think this note is descriptive enough. Won't be long before all anyone cares about is that it's supported in Safari 16+ :) |
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.
As of Sept 2024, Safari 16+ supports HTTP3 for all users.
Previously, a subset of users had support enabled (as long as they had Safari 14 or later (including Big Sur or later for Safari on macOS). There was a feature flag available in Safari 14.0-16.3 that allowed users to force HTTP3 on (it was removed for Safari 16.4+). Unlike other feature flags, having the flag off did not disable HTTP3, it just meant maybe the user got it, maybe they didn't.
It's complex to communicate all this in a dataset that assumes features ship with a new version of the browser. In this case, the changes are on being made elsewhere, and are not dependent on updating the browser.