-
Notifications
You must be signed in to change notification settings - Fork 60
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
feature(core): transform
is expanded to 3 different vendor prefixes
#379
Labels
💅 enhancement
New feature or request
Comments
We need to do more that What should be done?
|
layershifter
changed the title
feature(core): Jun 8, 2023
transform
is expanded to 3 different vendor prefixestransform
is expanded to 3 different vendor prefixes
|
ling1726
added a commit
that referenced
this issue
Jul 13, 2023
Copies the source from the [stylis prefixer](https://github.com/thysultan/stylis/blob/master/src/Prefixer.js) and updates it so that prefixing is only applied according the the browser support matrix. We follow the [browser support matrix](https://github.com/microsoft/fluentui/blob/master/rfcs/shared/build-system/06-browser-support-for-v9.md) of Fluent UI Fixes #379
ling1726
added a commit
that referenced
this issue
Jul 13, 2023
* feat: Prefix according to browser support matrix Copies the source from the [stylis prefixer](https://github.com/thysultan/stylis/blob/master/src/Prefixer.js) and updates it so that prefixing is only applied according the the browser support matrix. We follow the [browser support matrix](https://github.com/microsoft/fluentui/blob/master/rfcs/shared/build-system/06-browser-support-for-v9.md) of Fluent UI Fixes #379 * Change files * remote it.only * silence warnings
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using the css transform property, Griffel will expand this to include vendor prefixing for:
This results in a style rule that will have 4 times its length (including the actual transform) and negatively impacts bundlesize
The text was updated successfully, but these errors were encountered: