Safari supports HTTP/3 for all users now #7199
Conversation
|
This PR is not accurate, since HTTP3 support did not ship with Safari 18.0. It was enabled in the same month as Safari 18.0 but it applies to all users on Safari 16.0+. This is a weird feature. I talked to three of our engineers to nail down the historical details, and represent them in this PR: #7200 |
|
@jensimmons PR is also fair: You decide Fyrd! :) |
|
… aaand the simultaneous comment, haha :) |
|
I'm happy about the excitement!! Go HTTP3! I was going to create a PR like this, the way @Schweinepriester did... just make Safari 18.0 (or he did 18.1) solid green, while the previous versions stayed they way they've been... since, you know, that's literally how every other "Foobar just shipped!" PR works for Can I Use. But then as I discussed this with our engineers, I realized, no actually the day we made this change, we made it for every version of Safari 16.0+. It's impossible for anyone who is running Safari from the last two years of releases to not have this change. So... that's why I wrote the PR at #7200 the way I did. |
|
Yeah I went with @jensimmons 's PR in this case though certainly both approaches seemed reasonable. Thanks as always @Schweinepriester ! |
Fixes #7114.
Per #7114 (comment)
For now I would argue for
yfor 18.1+, because that is the first minor version released after 2024-09:https://developer.apple.com/documentation/safari-release-notes/safari-18_1-release-notes
18.0, released in 2024-09, could be either way from the start, but could also have been changed while it already was out, hence me playing it safe with 18.1.
While one could argue for
yfor all versions with the note, I feel like that would not represent the history as a retroactive change, though there's certainly room for debate.