- From: Chris Harrelson via GitHub <sysbot+gh@w3.org>
- Date: Sun, 27 Aug 2023 14:53:44 +0000
- To: public-css-archive@w3.org
> I agree that this the end goal, but specs usually need to describe the _how_, not just the high level goal. There are cases where certain details are left up to the UA, but typically there needs to be a reason, because the more details are left up to the UA, the more inconsistencies there are across browsers, and authors suffer as a result. If there is a better/faster algorithm to do this than gamut mapping both colors first, it's much better to talk it through and actually put it in the spec so that _all_ implementations could benefit :) You make a good point that there might be more UA inconsistencies as a result. However, I think there likely is not an algorithm that interoperably takes into account all OS/monitor hardware aspects, because monitors vary in their implementation. At this point, though, we're (or Chromium is, at least) at the experimental phase. Chromium intends to prototype the level 5 black/white `contrast-color()` feature, and we'll learn more from that prototyping. -- GitHub Notification of comment by chrishtr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8539#issuecomment-1694688521 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 27 August 2023 14:53:47 UTC