- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Mon, 10 May 2021 15:50:20 +0000
- To: public-houdini-archive@w3.org
> > From the June 2020 Houdini minutes it seemed that there was consensus to have a color object, regardless of how it had originally been specified - so that there can be color conversion, color manipulation, and extras like WCAG contrast ratio, gamut mapping, and so forth. > > Right, and that should be a Color class (and whatever appropriate subclasses, I trust you and Lea to have the best input on the shape of that API). But it should not be a _CSS_ color class as it's representing a color, not a CSS construct. And it should not be in this module (and arguably should not be a CSS module either as it should also be used in Canvas APIs, etc). > > We should be able to convert from the CSS color constructs to a Color object and vice-versa. The Color class should have all the conversion, manipulation, and extra functionality, not the CSS color objects (though I'm happy to add convenience methods to the CSS color classes once we've defined the Color class(es)). > > I fear the two concepts have become conflated here. Note that what @svgeesus and I were concerned about, that people will start using `CSSColorValue` in lieu of a `Color` class is already happening: https://github.com/fserb/canvas2D/blob/master/spec/color-input.md -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/1014#issuecomment-836868584 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 10 May 2021 15:50:22 UTC