[go: up one dir, main page]

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTP/3 usage might be underestimated, what does "partial support" i.e. "Enabled by default for a portion of users" really mean? #7114

Closed
PallHaraldsson opened this issue Jul 21, 2024 · 6 comments

Comments

@PallHaraldsson
Copy link
PallHaraldsson commented Jul 21, 2024

See:
https://caniuse.com/http3

Support could be as low as 75.86% or as high as 98% so it matters which and the numbers only depend on availability on Apple products.

E.g., for "tracked mobile" the "22.22%" "partial support" to get to 98.08% depends on how many users of Safari 14 up to 17 have have it enabled.

This "Enabled by default for a portion of users." seems like A/B testing, and wouldn't Apple have enabled for all users be now? Can someone test for me and see if HTTP/3 doesn't work for some version on iOS or macOS? To give me some confidence inn the low (or high) number.

It doesn't seem plausible that Apple enabled first for only some users with 14.4 in Sept 2020 and is still doing it year later with 17.5, so simply wrongly marked/not updated here?

@Schweinepriester
Copy link
Contributor

Please see the discussion in this PR: #6664

The last update at the time of writing:

I don't believe anything changed in our HTTP3 support. We did not announce a change in our Safari 17.0 release notes or article. I am looking into it.

@jensimmons
Copy link
Contributor

Safari now supports HTTP3 for all users, as of September 2024, no matter which version of Safari they are running.

@Schweinepriester
Copy link
Contributor

Wuhu, say no more, PR incoming!

@jensimmons
Copy link
Contributor

@jensimmons
Copy link
Contributor
jensimmons commented Oct 30, 2024

It's a complicated PR, but I think this properly conveys the message. See the note in the PR for more details. Also, I triple checked the history of what changed when with three engineers here at Apple.

@Schweinepriester
Copy link
Contributor

the autoclose didn’t work, but I believe this issue can be closed now :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants