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
Much of the preliminary work we've done in bedrock for the new Mozilla branding has hinged on custom properties and eschewed Sass variables. And frankly it simplified SO MUCH. It makes theme-switching and color modes much easier to implement without worrying about Sass compile errors or importing things in the right order.
Much of the preliminary work we've done in bedrock for the new Mozilla branding has hinged on custom properties and eschewed Sass variables. And frankly it simplified SO MUCH. It makes theme-switching and color modes much easier to implement without worrying about Sass compile errors or importing things in the right order.
We semi-recently converted Protocol to use custom properties for theming but preserved the Sass variables as fallbacks for older browsers. But looking at support levels and browser usage stats, I've been thinking it's time to embrace the future of CSS and remove those legacy Sass variables (at least for all the theme-level properties; some things can/should remain as Sass variables and mixins).
The text was updated successfully, but these errors were encountered: