- From: Elsie Hupp via GitHub <sysbot+gh@w3.org>
- Date: Fri, 10 Sep 2021 11:25:49 +0000
- To: public-css-archive@w3.org
Another reason for `<kelvin()>` to be in the spec (and implemented on the browser level) is indeed that it involves so many layers of translation, and the browser itself is in the best position to know, e.g., what the actual rendered colorspace is, so that, say 2700 kelvin (e.g. approximately an incandescent bulb at full brightness) actually ends up being rendered as 2700 kelvin. Like, if there is an accessibility color filter (say, also 2700 kelvin) in use on the client operating system, should 2700 kelvin render “through” the color filter in order to still be 2700 kelvin? Or should the specified 2700 kelvin itself have its white point be shifted by the color filter and render as something else? If the `<kelvin()>` function is specified as an accessibility aid, the specification might treat it differently than other `<color>` values. In so doing, browsers might treat `<kelvin>()` colors as absolute and counteract any operating-system-level white-point filter, though `<color>` values being specified as absolute vs dependent on operating-system-level white-point filters is probably a separate issue. (This issue kind of achieves the same purpose as the second part of my initial issue, just by different means, without exposing this information to the website. I can edit the above text to reflect this.) Basically, it should be an accessibility preference at the browser or system level whether websites or individual colors can specify an absolute white point and override any accessibility filters in place. This could help in the use cases of, e.g., cinematic color grading or professional photo editing, where certain color elements generally need to be calibrated as “accurate”, while other color elements (e.g. parts of the interface) generally don’t. -- GitHub Notification of comment by elsiehupp Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6582#issuecomment-916831854 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 10 September 2021 11:25:51 UTC