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
{{ message }}
Repository navigation
[css-color-hdr] dynamic-range-limit-mix() should take an arbitrary number of components (like color-mix(), calc-mix(), etc.) #14454
It's a bit weird that this one mix function normalizes nested mix() functions into a single non-nested mix() function for computed value. That seems like something all mix() functions should do, or none of them.
Activity
svgeesus commentedon Sep 7, 2026
Agreed. The prose already says that:
but the grammar needs to be updated.
[css-color-hdr] Update grammar of dynamic-range-limit-mix() to take o…
svgeesus commentedon Sep 7, 2026
WPT need to be reviewed for this change
weinig commentedon Sep 7, 2026
@svgeesus how about making the
<percentage>optional as well, to match the other mix functions?weinig commentedon Sep 7, 2026
Also, I wonder if it would be practical to use the standard mix() normalization algorithm instead of the bespoke one in https://drafts.csswg.org/css-color-hdr/#computing-dynamic-range-limit.
It's a bit weird that this one mix function normalizes nested mix() functions into a single non-nested mix() function for computed value. That seems like something all mix() functions should do, or none of them.
svgeesus commentedon Sep 8, 2026
@ccameron both these suggestions seem reasonable to me, what do you think?
@weinig the bespoke, multi-input normalization algorithm by @ccameron-chromium predates both the Values 5 mix normalization algorithm and the
color-mix()multi-color upgrades by @tabatkins .