Open Bug 1858813 Opened 1 year ago Updated 1 year ago

Create clearer names for button/input tokens

Categories

(Toolkit :: UI Widgets, task)

Product:
Toolkit
Component:
UI Widgets
Type:
task

Tracking

()

People

(Reporter: mstriemer, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [recomp])

We have some tokens for buttons that seem to be used for non-buttons, eg --button-background-color may be used for a checkbox's unchecked state.

We have some tokens for buttons that don't seem to fit a pattern, or are ambiguously named, eg --button-ghost-background-color (what does "ghost" mean) or -button-{,primary-,dangerous-,ghost-} (why isn't "primary" used most and why is the non-named one the most common)

There are likely more and perhaps it doesn't make sense to do all of these in one ticket.

Whiteboard: [fidefe-reusable-components] → [recomp]
You need to log in before you can comment on or make changes to this bug.