- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Mar 2023 20:56:05 +0000
- To: public-css-archive@w3.org
> [This part](https://drafts.csswg.org/css-color-4/#powerless) is just plain wrong: [...] Saying that missing components get treated as zero is fine (but assuming that always happens is not fine; in interpolation the missing component is treated as the analogous component in the other color). Saying that zero-valued components are always missing, on the other hand, is just wrong. I don't understand what you mean by this. The spec does not say that zero-valued components are missing. It says that certain components, when zero-valued, can cause *other* components to be powerless (and thus missing, after conversions). Your comment appears to be a non sequitur? > I agree the current specification is perfectly clear to do this; but as I https://github.com/w3c/csswg-drafts/issues/8609#issuecomment-1489087190 the current specification is completely incorrect to make Chroma powerless here. It is zero, not unknown or missing. Hue is missing, sure (although that then gives a discontinuity when L rises to, say, 0.001). Chroma is powerless when lightness is 0% because any chroma value results in the exact same color (black). (And maybe the same is true of white, I forget the outcome of our conversation about this earlier.) Powerless is not missing or unknown. The component is zero, and also powerless (because of the lightness, not because of its own value). I sincerely don't understand what in the spec you're objecting to, here. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8609#issuecomment-1490947834 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 30 March 2023 20:56:07 UTC