- From: Christoph Päper via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Jan 2020 14:49:19 +0000
- To: public-css-archive@w3.org
@LeaVerou: >- Interpolation between colors of the same color space is done in that color space >- Interpolation between colors of different color spaces, where one color space is a strict subset of the other is done in the wider color space >- Any other interpolation is done in Lab I think we could relax the second rule to only affect strict supersets of sRGB. We could also amend the third rule if it was possible for the author or user to explicitly select a working color space. By the way, are color keywords necessarily in sRGB? Static predefined ones probably are, but what about `currentcolor` and system colors? Perhaps we could combine a _global working color space_ per stylesheet #300 with _local working color spaces_ per element or per style rule. - Interpolation between colors is done in in the local working color space. - The _default local working color space_ is sRGB. - The _implied local working color space_ is * CIELAB if `lab()` or `lch()` notation is used for one of the base colors or for `currentcolor`, * otherwise CMYK if `device-cmyk()`, * otherwise the color space used in `color()` notation if there is only one being used, not counting sRGB, * otherwise the explicit local working color space if specified, * otherwise the default local working color space (sRGB). - The _explicit local working color space_ is defined by the new inherited **`color-space` property**, defaulting to the global working color space, but perhaps initialized to CIELAB. - The _global working color space_ is defined by the **`@color-space` at-rule**, defaulting to sRGB. -- GitHub Notification of comment by Crissov Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4647#issuecomment-572103066 using your GitHub account
Received on Wednesday, 8 January 2020 14:49:21 UTC