- From: Elsie Hupp via GitHub <sysbot+gh@w3.org>
- Date: Tue, 21 Dec 2021 15:44:10 +0000
- To: public-css-archive@w3.org
Hi @svgeesus— I could imagine multiple possible use cases for a `<kelvin()>` color-function. While, yes, one web designer might want to create a chromatic adaptation, a different web designer might want to use a color in its absolute state, and yet another web designer might want to use it as an input for some as yet unforeseen function. If CCT chromatic adaptation can be easily produced using the absolute color value (from `<kelvin()>`) and one or more existing [blend modes](https://developer.mozilla.org/en-US/docs/Web/CSS/blend-mode), it might be unnecessary to create a new “white balance” blend-mode function exclusively for the purpose of chromatic adaptation. On the other hand, an explicit “white balance” function (or set of functions) might still be a welcome convenience for some designers. The main reason I suggest the `<kelvin()>` color-function itself as a convenience is that Kelvin color values are increasingly used in marketing materials (for LED luminaires), so designers might increasingly be thinking in those terms, rather than exclusively in the terms of pixel color values, pigment color values, etc.; and the math for translating a Kelvin blackbody locus to the color on a computer display is well enough established that it should be relatively trivial for browser vendors to implement. -- GitHub Notification of comment by elsiehupp Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6582#issuecomment-998885802 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 21 December 2021 15:44:11 UTC