Re: [css-houdini-drafts] CSSColorValue.colorSpace restricts naming of future color functions and color() keywords (#1070)

Yeah we keep going back and forth about which or even whether color functions should be representable in `color()`.

But let's step back for a bit.

Do we actually need a `.to(colorSpace)` method in `CSSColorValue`? It cannot actually convert in many cases (e.g when values contain variables or relative values of some sort), and I believe was added as a stopgap before we resolved to have a separate `Color` class. I think conversions make more sense to be handled by the `Color` class, which would only accept resolved values and thus wouldn't have the problem of only being able to convert sometimes. It will be more verbose, but I think the predictability is worth it.

-- 
GitHub Notification of comment by LeaVerou
Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/1070#issuecomment-1103241257 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 19 April 2022 22:56:06 UTC