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.
Part of #44921 (comment)
Context
Emotion keeps a local copy of the stylis prefixer to only apply the prefixes they consider necessary. Emotion will likely remove all of the prefixes in v12, but that might take some time to land. See related PR emotion-js/emotion#3296
We tell users to use the stylis prefixer in our docs. Although most of the CSS properties shouldn't be prefixed anymore using the stylis prefixer because they're widely available, there are a few properties that still require a prefix (see comments in this Emotion PR, which keeps their own local copy of the stylis prefixer:
color-adjust
box-decoration-break
mask
,mask-image
,mask-(mode|clip|size)
,mask-(repeat|origin)
,mask-position
,mask-composite
user-select
,hyphens
,text-size-adjust
It's not safe to remove the stylis prefixer just yet, because of this. The ideal path forward would be for stylis to be less defensive and remove widely supported prefixes in a new version, but it's not clear which are the browsers that stylis wants to support.