- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Tue, 22 Aug 2023 13:53:12 +0000
- To: public-css-archive@w3.org
> Let me clear something up. My library will not assume hue is powerless like CSS does when an explicit hue is provided (conversion may cause a hue to go powerless). So I am not demonstrating how a browser should handle chroma. Isn't it confusing to go beyond the scope of CSS and expected browser behavior? To me this feels like comparing apples and oranges and it keeps throwing me off balance. I will gladly admit that I am often incorrect here and that I make many mistakes both in statements here and in implementations. So I welcome anything that challenges my assumptions. But I think it would be best to keep everything focussed on CSS and expected browser behavior. I also try to avoid comparing with tools that go beyond the scope of CSS because it is too easy to get lost in what is essentially user error. ------- As far as I know these things are true : - when interpolating with a missing component you should take the component from the other color - powerless components can become missing components at specific points - `hue` becomes powerless when `chroma` is `0` So when applying this by hand : - `oklch(75% 0% 60deg)` - `oklch(75% 50% 0deg)` - `lightness` is `75%` in both colors, so outcome is `75%` - `chroma` is `50%` and `0%`, so outcome is `25%` - `hue` is `60deg` and `0deg`, but `60deg` is powerless given the `0%` chroma, outcome is `0deg` - final result is `oklch(75% 25% 0deg))` Ignore any tool, library, browser implementation. This is simply taking the sum of components and dividing by 2, or even simpler, just taking the component from one of the source colors. Are these steps correct for the current latest versions of all relevant specifications? -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8609#issuecomment-1688233855 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 22 August 2023 13:53:15 UTC