I went through the Radix UI docs on color scales, and while reading, I noticed a gap in the concept for button states. Specifically, the setup for states like 3 normal, 4 hover, and 5 pressed with brand colors 9 normal and 10 hover isn't fully supported—there's no pressed state color defined.
I then checked out the components shown in the documentation, as they do have a distinct color for the pressed state that differs from hover. And guess what? They’re using filters. I find it a bit disappointing to see filters being applied in such a well-thought-out system. In fact, multiple filters are defined there.
So, my question is: why are additional colors being generated through filters instead of creating a palette that accounts for this common use case? Or, is using filters the only viable solution here?
I went through the Radix UI docs on color scales, and while reading, I noticed a gap in the concept for button states. Specifically, the setup for states like 3
normal
, 4hover
, and 5pressed
with brand colors 9normal
and 10hover
isn't fully supported—there's nopressed
state color defined.I then checked out the components shown in the documentation, as they do have a distinct color for the
pressed
state that differs fromhover
. And guess what? They’re using filters. I find it a bit disappointing to see filters being applied in such a well-thought-out system. In fact, multiple filters are defined there.Active Button:
Vars:
So, my question is: why are additional colors being generated through filters instead of creating a palette that accounts for this common use case? Or, is using filters the only viable solution here?