- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Mar 2021 02:03:06 +0000
- To: public-css-archive@w3.org
> Y'all just keep saying "when you convert a color", but as far as I can tell Color 4 doesn't have any way to do so that doesn't immediately fill in a hue anyway. I think the concept you are missing, in general about CSS Color 4 (explicitly) and all colors back to CSS 1 (implicitly) is that they have a **colorimetric basis**. They are tied to scientific, rigorous, measurable color sensations. [CSS Color 4 tries](https://drafts.csswg.org/css-color-4/#terminology) to explain that, with a balance between completeness and readability. This means that I see "a bunch of different ways to specify a color" with great care taken to say *exactly what color that is*. While you, I think, focus far more on "here are a bunch of different syntaxes" and what measured color that actually is, is sort of a by product. Which explains the disconnect over the color part of Typed OM. You see it as deeply tied to syntax, while I see it as a way to set, query and manipulate color. And thus *of course* if the author sets a color in syntax A they need to be able to get that color in syntax B or C or Z because the crucial thing is *getting the color* and indeed *getting the right color*. So yes, CSS Color 4 does not give a way to _get_ a color in any given colorspace *because it is not an object model*. But it provides all the math and description to enable that conversion between colorspaces. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6107#issuecomment-805416589 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 March 2021 02:03:14 UTC