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
The current implementation helpfully adds browser-specific prefixes to CSS elements which need them by parsing CanIUse data and turning that into a Scala source file as described here: https://japgolly.github.io/scalacss/book/dev.html
However, it appears (I could be wrong) that misc/caniuse.scala's strategy for computing Partial / Full / etc Support is based on looking at every version of the browser in question that has ever existed. For instance, while the flex family of CSS elements have been fully supported in Safari since 2015, because any prior versions exist in the CanIUse JSON file, properties like display: -webkit-flex; are output in generated CSS.
It would be nice to be able to "draw a line in the sand" in time, version history, relative number of versions back, anything like that, so that we do not generate excessive browser-specific prefixes.
In the mean time, is there a work-around to simply turn auto-injecting extra prefixed properties off altogether?
Thank you!
The text was updated successfully, but these errors were encountered:
The current implementation helpfully adds browser-specific prefixes to CSS elements which need them by parsing CanIUse data and turning that into a Scala source file as described here: https://japgolly.github.io/scalacss/book/dev.html
However, it appears (I could be wrong) that
misc/caniuse.scala
's strategy for computingPartial
/Full
/ etcSupport
is based on looking at every version of the browser in question that has ever existed. For instance, while theflex
family of CSS elements have been fully supported in Safari since 2015, because any prior versions exist in the CanIUse JSON file, properties likedisplay: -webkit-flex;
are output in generated CSS.It would be nice to be able to "draw a line in the sand" in time, version history, relative number of versions back, anything like that, so that we do not generate excessive browser-specific prefixes.
In the mean time, is there a work-around to simply turn auto-injecting extra prefixed properties off altogether?
Thank you!
The text was updated successfully, but these errors were encountered: