7

make toolkit our source of truth for CSS token values/variables

 1 year ago
source link: https://bugzilla.mozilla.org/show_bug.cgi?id=1798404
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

Details

(Whiteboard: [fidefe-reusable-components-ms1])

Currently our reusable widgets in toolkit rely on variable values defined in in-content/common-shared.css

This has led to issues when these widgets are used in chrome contexts. It also means that the lit based components we're currently building have an implicit dependency on that CSS file having been loaded somewhere in the contexts in which they are being used.

As a solution to the issues we've encountered we want to create a CSS tokens/variables file in toolkit that can be shared between in-content and chrome. This will be our source of truth for component variable values going forward (specifically for things like colors, spacing, etc). The names used should match the variable names used by design to facilitate better communication and smoother dev/design handoffs.


About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK