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

Mapping of Safari Tech Previews to actual Safari releases? #2991

Closed
Elchi3 opened this issue Oct 15, 2018 · 11 comments
Closed

Mapping of Safari Tech Previews to actual Safari releases? #2991

Elchi3 opened this issue Oct 15, 2018 · 11 comments
Labels
data:browsers Data about browsers (versions, release dates, etc). This data is used for validation. question Issues where a question or problem is stated and a discussion is held to gather opinions.

Comments

@Elchi3
Copy link
Member

Elchi3 commented Oct 15, 2018

The Safari docs and support information sources are sparse. This makes it hard to review data update PRs. The Safari TP release notes are quite good, however. Does anyone know how you can map TP versions to actual Safari versions?

What we know:
TP 1-13: Safari 10
TP 14-20: Safari 10.1
TP 21-36: Safari 11
TP 37-47: Safari 11.1
TP 48-58: Safari 12
TP 59-76: Safari 12.1
TP 77-89: Safari 13
TP 90-98: Safari 13.1
TP 99-109: Safari 14
TP 110-122: Safari 14.1
TP 123-129: Safari 15

@Elchi3 Elchi3 added the question Issues where a question or problem is stated and a discussion is held to gather opinions. label Oct 15, 2018
@a2sheppy
Copy link
Contributor

That's a good idea, potentially.

The bigger problem in the short term, I think, is that we currently have no way to indicate that a feature landed in a particular TP version. The notion of the browser actually having different version number standards in its developer build releases is not something our schema allows for.

@Elchi3
Copy link
Member Author

Elchi3 commented Apr 6, 2019

Good news, everyone! At least for Safari 12.1 Apple provides us with such a mapping, see the release notes: https://webkit.org/blog/8718/new-webkit-features-in-safari-12-1 all the way down to "Feedback":

"Changes in this release of Safari were included in the following Safari Technology Preview releases: 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76."

So, that's a lot of features we could mark as "12.1".

@Elchi3
Copy link
Member Author

Elchi3 commented Apr 18, 2019

For Safari 11:

"Changes in this release of Safari were included in the following Safari Technology Preview releases: 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36."

Source: https://webkit.org/blog/7956/new-webkit-features-in-safari-11/

@queengooborg
Copy link
Contributor

For Safari 10.1:

"The changes included in this release of Safari span Safari Technology Preview releases 14, 15, 16, 17, 18, 19, and 20."

Source: https://webkit.org/blog/7477/new-web-features-in-safari-10-1/

@craigkovatch
Copy link
Contributor

craigkovatch commented Sep 11, 2019

Apple also removed the release notes for Safari <12 from their developer pages :( Anyone have a contact there they could ping?

@queengooborg queengooborg added the data:browsers Data about browsers (versions, release dates, etc). This data is used for validation. label Sep 29, 2019
@queengooborg
Copy link
Contributor

The following blog post makes it sound like Safari TP 84 is when changes are frozen for Safari 13's release: https://webkit.org/blog/9170/safari-technology-preview-84-with-safari-13-features-is-now-available/

@a2sheppy
Copy link
Contributor

a2sheppy commented Oct 7, 2019

We should start archiving copies of release notes for browsers, so that we have access to them even if the developer decides to remove them from their site.

@Elchi3
Copy link
Member Author

Elchi3 commented Mar 16, 2020

https://webkit.org/blog/9674/new-webkit-features-in-safari-13/ says "changes in this release of Safari were included in the following Safari Technology Preview releases: 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89."

Thus updated our mapping for Safari 13.
Still waiting on something for Safari 13.1.

@LeaVerou
Copy link
Contributor

Tried to update compat data for various color features that were introduced in Safari TP 120 and 121, but since they haven't launched yet, I'm not sure what Safari version to add. Any ideas?

LeaVerou added a commit to LeaVerou/browser-compat-data that referenced this issue May 28, 2021
I used `"TP"` for features that are in Safari TP and have not yet shipped. I also asked [here](mdn#2991 (comment)).
Note that Safari 10 only supported color(display-p3). The other predefined color spaces were added recently and are still in TP. We can iterate on breaking this down in future PRs.
@queengooborg
Copy link
Contributor

We've yet to allow data to be added for Safari TP versions, but are now working on it -- see #10334.

queengooborg added a commit to queengooborg/browser-compat-data that referenced this issue Jul 25, 2021
This PR adds real values for Safari (Desktop and iOS/iPadOS) for the `Worker.options_name_parameter` member of the `Worker` API.  By using the mapping in mdn#2991, I've set the appropriate version numbers based upon their matching TP edition.  Fixes mdn#6455.
@Elchi3
Copy link
Member Author

Elchi3 commented Feb 9, 2022

This is resolved now given we allow "preview" as a version number.

The Safari team has also updated "preview" values to the actual Safari version numbers whenever a feature ships in Safari stable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data:browsers Data about browsers (versions, release dates, etc). This data is used for validation. question Issues where a question or problem is stated and a discussion is held to gather opinions.
Projects
None yet
Development

No branches or pull requests

6 participants
@LeaVerou @Elchi3 @a2sheppy @queengooborg @craigkovatch and others