- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 Jul 2024 14:01:52 +0000
- To: public-css-archive@w3.org
> I'm filing a new issue, because [since Chrome 120](https://chromiumdash.appspot.com/commit/71a936c76e12c63c3a4bee4034b5054151fdc55c), lightness exactly equalling 0 or 100% are mapped to black and white respectively. This led to a [discontinuity](https://issues.chromium.org/issues/329106317) and browsers now handle these cases differently: > > https://wpt.live/css/css-color/oklab-l-almost-0.html (subtle difference) https://wpt.live/css/css-color/oklab-l-almost-1.html (very apparent difference) > > See also [results on wpt.fyi](https://wpt.fyi/results/css/css-color?label=master&label=experimental&aligned&q=almost) > > In [web-platform-tests/wpt#45073 (comment)](https://github.com/web-platform-tests/wpt/pull/45073#issuecomment-2002106428), @svgeesus explained that the spec previously "effectively mandated a discontinuity", but that's no longer the case, so Chrome appropriate fails these tests now. Looking at this test and the results (in Firefox Nightly and Chrome Canary, I don't have an Apple device handy to check Safari rn) I observe that Chrome passes the test currently and we have interop across three browsers reported on wpt.fyi. The behavior mandated by the WPT test conforms to the current CSS Color 4 spec text, and we no longer have the undesirable discontinuity. Declare victory and close? -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10109#issuecomment-2220593870 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 10 July 2024 14:01:53 UTC