- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 May 2021 12:35:43 +0000
- To: public-houdini-archive@w3.org
Agreeing with @plinss and @LeaVerou here. @litherum [wrote](https://github.com/whatwg/html/issues/5616#issuecomment-641103422) > Presumably, **CSS Typed OM will want a color type**. We should make sure that we don't have two competing color types. Instead, the same type should work for both. @fserb [wrote](https://github.com/whatwg/html/issues/5616#issuecomment-777607775) > We had a conversation with the CSS WG and **CSS Typed OM is very close to have a Color type**. Given that, we are working on modifying this to simply support the Typed OM color type described here: https://drafts.css-houdini.org/css-typed-om-1/#colorvalue-objects So people are assuming that the color type in CSS Type OM is **the color type for the Web platform.** And honestly, Canvas people should not be penalized for trying hard to align with CSS Color 4 here and re-using CSS stuff in Canvas. Yes, Typed OM needs to reflect whatever was used to construct a given color. But at the end of the day, it is being used to set and query colors; and colors have meaning, and the same actual color can be set in multiple syntactic ways and still be the same color. So there is a need for a color type. Colors can also be compared with other colors, and whatever syntax was used to create that pair of colors is irrelevant to that comparison operation. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/1014#issuecomment-838398134 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 May 2021 12:35:47 UTC