You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running a test of the CSS used on our site, we get a low score for the heavy use of old prefixes applied, many of these are coming from the swiper package. I can see that autoprefixer is used, but is there any way to either disable that or update it in the package, since we do not support older browsers that need these prefixes
These are the use cases the following applies to, that we do not need
Required by Android Browser 4.4, Chrome 35, iOS Safari 8.1, Opera 22, Safari 8 and earlier
The following are examples of prefixes that would only be necessary if supporting the above browsers
-webkit-transform
-webkit-perspective
-webkit-transform-style
-webkit-transform-origin
If I could just make a setting of what browsers should be supported, kind of what I do in my package file by using browserslist settings. I would argue that the support setup in the package right now is too wide, these are most recent stable versions of browsers and many go 2-5 versions back.
Chrome 101, Edge 101, Firefox 100, Opera 86, Safari 15.4
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When running a test of the CSS used on our site, we get a low score for the heavy use of old prefixes applied, many of these are coming from the swiper package. I can see that autoprefixer is used, but is there any way to either disable that or update it in the package, since we do not support older browsers that need these prefixes
These are the use cases the following applies to, that we do not need
Required by Android Browser 4.4, Chrome 35, iOS Safari 8.1, Opera 22, Safari 8 and earlier
The following are examples of prefixes that would only be necessary if supporting the above browsers
-webkit-transform
-webkit-perspective
-webkit-transform-style
-webkit-transform-origin
If I could just make a setting of what browsers should be supported, kind of what I do in my package file by using browserslist settings. I would argue that the support setup in the package right now is too wide, these are most recent stable versions of browsers and many go 2-5 versions back.
Chrome 101, Edge 101, Firefox 100, Opera 86, Safari 15.4
Beta Was this translation helpful? Give feedback.
All reactions