- From: Mingye Wang via GitHub <sysbot+gh@w3.org>
- Date: Sat, 20 Feb 2021 13:36:06 +0000
- To: public-css-archive@w3.org
Artoria2e5 has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-color] profiled colors can be device-independent == The current [css-color-4, chapter 10](https://drafts.csswg.org/css-color-4/#icc-colors) is titled "Profiled, Device-dependent Colors". This title seems to neglect the existence of [ColorSpace profiles](http://www.colorwiki.com/wiki/The_7_ICC_Profile_Types), which are used to specify a device-independent colorspace. CIELAB is quite a lot better than doing stuff in RGB, but some of its flaws (blue hue, etc.) are quite well known. There is a point in using such an alternate profile in the blending defined in css-color-5, or to pick colors out of an alternate lch-style wheel in css-color-4 using `color()`. This change does not alter the data-model of `color()`. The specification should probably add an exhaustive list of the ICCv4 profile types (see http://www.color.org/specification/ICC1v43_2010-12.pdf#page=36). I am pretty sure that only the Input, Display, Output, and ColorSpace types are good candidates for specifying colors anyways. DeviceLink has no information about a colorspace the system itself uses; Abstract is for... fun; and NamedColor certainly doesn't work with the pass-in-floating-point-number model. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6024 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 20 February 2021 13:36:08 UTC