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

Add "iPadOS" to label of the "Safari on iOS" column #6326

Closed
a2sheppy opened this issue Jun 24, 2020 · 9 comments
Closed

Add "iPadOS" to label of the "Safari on iOS" column #6326

a2sheppy opened this issue Jun 24, 2020 · 9 comments
Labels
data:browsers 🌍 Data about browsers (versions, release dates, etc). This data is used for validation. idle 🐌 Issues and pull requests with no recent activity

Comments

@a2sheppy
Copy link
Contributor

We currently label the mobile Safari column "Safari on iOS". We should change this to either "Safari on iOS/iPadOS" or "Safari (iOS/iPadOS)". This will help to ensure clarity.

@Elchi3
Copy link
Member

Elchi3 commented Jun 24, 2020

The current labeling was discussed with Apple and approved by them, so I don't think we should just change this.
@apple-web-evangelist, what do you think about this suggestion?

@ddbeck ddbeck added the data:browsers 🌍 Data about browsers (versions, release dates, etc). This data is used for validation. label Jun 24, 2020
@a2sheppy
Copy link
Contributor Author

a2sheppy commented Jun 24, 2020 via email

@ddbeck
Copy link
Collaborator

ddbeck commented Jun 25, 2020

See https://github.com/mdn/browser-compat-data/blob/master/docs/data-guidelines.md#safari-for-ios-versioning and #2006 for background on this.

I'm disinclined to do this without some reassurances from Apple that iOS and iPadOS data is strictly equivalent. To change the identifier for iOS to also cover iPadOS now would be a strong retroactive claim about the data. For example, we haven't been asking contributors to show some evidence for both iOS and iPadOS when we're reviewing iOS data. If we changed the identifier, it might give people a false idea about the rigor of that data.

@othermaciej
Copy link

Maybe it should be a separate column? There's some things that are available in iPadOS Safari but not iOS (for example, Media Source Extensions), and I think also vice versa. Another example is Fullscreen API.

@queengooborg
Copy link
Collaborator

iOS and iPadOS are still just about the same OS at this point, and I doubt there will be much compatibility differences in the future. As such, I don't think that creating a new column and a new browser entry are the right way to go about it. Since there are few differences in compatibility between Safari for iOS and Safari for iPadOS, using notes has been sufficient.

Of course, there could be major compatibility changes down the line. Let's see what Apple wants us to do going forward!

@othermaciej
Copy link

We prefer to align Safari for all platforms when possible, but when there's a split, in the future it will more likely be between macOS+iPadOS on the one hand, and iOS on the other.

@queengooborg
Copy link
Collaborator

(I just saw your profile and realize that you work at Apple, @othermaciej -- oops, sorry for not noticing before!)

@othermaciej
Copy link

No worries, I didn't exactly highlight it. We'll try to come up with a proposal for the best way to handle this issue too.

@a2sheppy
Copy link
Contributor Author

a2sheppy commented Aug 3, 2020

No worries, I didn't exactly highlight it. We'll try to come up with a proposal for the best way to handle this issue too.

Good deal. I'm fine with dropping this for now then. Glad to have had this discussion though!

@github-actions github-actions bot added the idle 🐌 Issues and pull requests with no recent activity label May 25, 2022
@Elchi3 Elchi3 closed this as completed Aug 10, 2023
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. idle 🐌 Issues and pull requests with no recent activity
Projects
None yet
Development

No branches or pull requests

5 participants