- From: Isaac Muse via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Mar 2023 15:34:11 +0000
- To: public-css-archive@w3.org
> I have no strong opinion about this and it was also not the focus of this issue :)
Well, it's related to the fact that it would help steer the resolution on a consistent powerless approach. I feel others may come to a similar conclusion that you did, so being clear about what is ideal and not ideal is important when attempting to resolve the confusion and get everyone on board with the same convention. CSS may go against my personal opinions in this regard, but I think it is important to lay out the reasons.
> Currently the specification requires powerless components to become missing when converting between color spaces and states that both c and h are powerless for an L of 0/1 in oklch.
Yep, and I think that is a mistake. I think "powerless" for LCh chroma or Lab a and b, if such a thing must be enforced, _should_ mean zero. Hue is a bit special and makes sense to be missing for interpolation of achromatic colors.
There are some color spaces where zero doesn't always make sense for chroma, JzCzhz actually has an exponential chroma response for achromatic colors as lightness increases, though it is still low enough that you can probably get away with clamping it at the loss of only a little accuracy. Google's new HCT color space gets really high (as far as chroma goes) because it's based on CAM16 without discounting, but I'm getting off-topic now 🙂.
```py
>>> Color('white').convert('jzczhz', norm=False)
color(--jzczhz 0.22207 0.0002 216.08 / 1)
>>> Color('white').convert('cam16-jmh', norm=False)
color(--cam16-jmh 100 2.2369 209.53 / 1)
```
--
GitHub Notification of comment by facelessuser
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8609#issuecomment-1490513575 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 15:34:13 UTC