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
See how we might use PostCSS custom properties to provide fallback for older browser that don't understand custom properties.
Would be good to understand if/how it would work for more complex things like having variables in media queries.
Why
Not all browsers support custom properties, so we need to find a plan for providing users a decent experience in those. The plugin looks promising but we need to understand exactly what it provides and where the pitfalls would be, if any.
Who needs to work on this
Developers
Who needs to review this
Developers
Done when
We've set up PostCSS custom properties on a branch, explored its used and documented how helpful it is and where it falls short.
The text was updated successfully, but these errors were encountered:
I've tested this briskly on IE11. Initially the foundational colours and fonts weren't coming through in the review app, which was because the review app itself wasn't post-processing it's CSS so I needed to add the plugin to the review app as well.
I'm concerned this means that in order to reap the benefits of the plugin, users need to install the plugin into their build process. My hope is that this is just a result of how we process the review app. I'm going to test this further by creating a preview release and porting it to the design system website.
From creating a release preview in the design system, unfortunately it looks like my concern was true. Postcss doesn't apply to users of the design system unless they're specifically using the minified CSS.
Something we could potentially explore to get around this is having a sass mixin that does this for us, meaning that the problem is solved at the pre-processing level and more users benefit from it.
What
See how we might use PostCSS custom properties to provide fallback for older browser that don't understand custom properties.
Would be good to understand if/how it would work for more complex things like having variables in media queries.
Why
Not all browsers support custom properties, so we need to find a plan for providing users a decent experience in those. The plugin looks promising but we need to understand exactly what it provides and where the pitfalls would be, if any.
Who needs to work on this
Developers
Who needs to review this
Developers
Done when
The text was updated successfully, but these errors were encountered: