- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Sun, 27 Aug 2023 00:04:49 +0000
- To: public-css-archive@w3.org
@chrishtr Great to hear that there are no implementation hurdles around this! I noticed you’re using "take into account OS and hardware gamut mapping" both in your comment, as well as your proposed spec text. Does this mean they plan to take it into account in a different way than what is proposed here? If not, I would prefer to use the more precise wording that implementations should gamut map both colors in a color pair to the gamut of the output device prior to applying any contrast calculations. Please note that the decision in this issue doesn't just affect Level 5 `contrast-color()` but also the more complex `contrast-color()` function in Level 6 which can return arbitrary colors. ---------- @svgeesus @danburzo I just realized an issue with what we're discussing. There can be multiple output devices, and CSS functions cannot return different used values in different output devices (can they?), not to mention the same element, with e.g. a flat background-color can be displayed across multiple screens at the same time. We also cannot ask implementations to gamut map to the intersection of the gamuts, a) because that's nontrivial to calculate and b) because this produces poor user experience (imagine connecting an auxiliary low quality screen to get some more space, and suddenly this affects your viewing experience everywhere!). Perhaps we can just use the gamut of the primary display device, which should be more stable? -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8539#issuecomment-1694526954 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 27 August 2023 00:04:51 UTC