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
Agree. We are too strict in validating colors because we rely on d3-color which does not support CSS Level 4 d3/d3-color#96 and other modern enhancements to CSS. I think we could be much more lenient here, allowing anything that looks like it might be CSS, including rgba(…), hsl(…), lch(…), oklab(…), without strictly validating or trying to parse the string. (We still need to check against the X11 named colors though!)
Closely related to #765.
It would be great if the
isColor
check supported native color functions with CSS vars inside. Some examples:rgba(255, 0, 0, var(--a))
rgb(var(--rgb))
hsl(240deg 50% var(--l))
hsl(var(--hsl) / 50%)
Thanks!
The text was updated successfully, but these errors were encountered: