- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Jun 2024 12:55:00 +0000
- To: public-css-archive@w3.org
cdoublev has just labeled a pull request from cdoublev for https://github.com/w3c/csswg-drafts as "css-color-4": == [css-color-4] CSS gamut mapping applies on actual values == This sentence in [13.2. CSS Gamut Mapping to an RGB Destination](https://drafts.csswg.org/css-color-4/#css-gamut-mapping) suggests that CSS gamut mapping is applied to get used values: > **TESTS** > > Used values of color are not exposed to script, making this hard to test in an automated manner. From my understanding, used values of color are exposed by [`getComputedStyle()`](https://drafts.csswg.org/cssom-1/#resolved-values): > - [...] > - `color` > - `outline-color` > - A resolved value special case property like `color` defined in another specification > > The resolved value is the [used value](https://drafts.csswg.org/css-cascade-5/#used-value). I guess the resolved value should not depend on the display device ([13.1. An Introduction to Gamut Mapping](https://drafts.csswg.org/css-color-4/#gamut-mapping-intro)): > [...] if the destination is the display device (a screen, or a printer) then out of gamut values must be converted to an in-gamut color. Therefore I think [*actual values*](https://drafts.csswg.org/css-cascade-5/#actual) was the expected term in the first sentence. See https://github.com/w3c/csswg-drafts/pull/10467 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 19 June 2024 12:55:01 UTC