Add Safari 10 to browserslist - #435
Merged
Merged
Conversation
tylersticka
reviewed
Jul 19, 2018
|
|
||
| > 4% | ||
| Last 1 version | ||
| Safari 10 |
Member
There was a problem hiding this comment.
Is there any benefit to making this Safari > 9 or similar, to prevent any future weird "gaps" where fixes are included for Safari 10 but not 11?
Member
Author
There was a problem hiding this comment.
Would Last 3 Safari versions do what we want it to?
Safari 11.1
Safari 11
Safari 10.1
Then it would require less maintenance, because it would automatically update when new versions are released.
Another thing that might be worth looking into is browserslist-ga. What do you think?
Member
There was a problem hiding this comment.
I do not have a strong opinion on how it's done as long as the version gap problem is solved.
Member
|
@tylersticka I updated to |
tylersticka
approved these changes
Mar 2, 2020
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
3 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.
If we are going to have workarounds to support Safari 10, we should also ensure that autoprefixer generates prefixes compatible with Safari 10 and that postcss-preset-env emits syntax compatible with Safari 10