- From: Aaron Krajeski via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Jul 2023 17:28:55 +0000
- To: public-css-archive@w3.org
> Yes, the discontinuity of powerlessness has been brought up before. It's an unfortunate but unavoidable consequence, if you want to keep solving the problems that powerlessness is designed to solve (which is: don't hallucinate a component value that the author didn't _and couldn't_ state in the original color space, just because a conversion shifted the color into a space where that component requires a value. Is this to say that this powerlessness is really only an issue for conversions _into_ the color spaces with lightness as a component? It's an interesting thing to try to design around, in my opinion, because there are many different whites that a user could be trying to express: `color(srgb 1 1 1)` = `lab(99.9988 0.0188053 -0.00110865)` or `lch(99.9988 0.0188379 356.626)` `color(xyz-d65 1 1 1)` = `lab(100 9.06837 5.79284)` or `lch(100 10.7607 32.5703)` `color(xyz-d50 1 1 1)` = `lab(100 6.11317 -13.2363)` or `lch(100 14.5798 294.79)` `lab(100 0 0)` is a different white entirely. To my eye they all look different. For the `xyz` whites the way they can exist in the `lab`/`lch` color spaces is with non-zero `a`, `b`, and `c` values. If a user asks for `xyz-d65` in `lch`, it doesn't seem to me that the `c` value is "hallucinated". -- GitHub Notification of comment by mysteryDate Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8794#issuecomment-1654076178 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 July 2023 17:28:57 UTC