- From: Sam Weinig via GitHub <sysbot+gh@w3.org>
- Date: Fri, 14 Feb 2025 03:30:34 +0000
- To: public-css-archive@w3.org
weinig has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-color-4] Define epsilon (or range of valid epsilons) for determining when Lab/OKLab should be considered achromatic == The current CSS Color 4 spec doesn't define specific values for when a Lab/OKLab color should be considered achromatic, stating: > For extremely small values of a and b (near-zero Chroma), although the visual color does not change from being on the neutral axis, small changes to the values can result in the reported hue angle swinging about wildly and being essentially random. In CSS, this means the hue is [powerless](https://drafts.csswg.org/css-color-4/#powerless-color-component), and treated as [missing](https://drafts.csswg.org/css-color-4/#missing-color-component) when converted into LCH or OKLCh; (https://drafts.csswg.org/css-color-4/#lab-to-lch) The lack of specificity here (and therefore lack of testability) has lead to incompatibility between browsers (see https://bugs.webkit.org/show_bug.cgi?id=287637 for an example). Is there some reason we cannot define what this "extremely small values of a and b (near-zero Chroma)" is? If defining specific constants is not ideal, perhaps some bounds? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11706 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 14 February 2025 03:30:35 UTC