- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Jun 2024 09:45:44 +0000
- To: public-css-archive@w3.org
> These contradict each other. Or at least to me they are conflicting :) Ah, they don't! On the one hand, as hardware advances, a color well outside of Rec2020 will radically change between how it looks on legacy monitors and how it looks on new monitors. Your pictures of tropical parrots and flowers will just get prettier and prettier. On the other hand, extremely vivid colors aren't actually *needed* (or even *desired*) for most use-cases; Rec2020 is (we think) a decent compromise space that covers the likely near-future usage of colors, and generally contains most colors people actually want to use. You don't actually *want* to render tropical-macaw red on your website most of the time, it's kinda blinding. The problem is that while extremely vivid colors aren't *needed* for most things, they're very easy to *specify*, including accidentally via innocent-looking color modification (hue rotation, lightening, etc). Someone designing their page, today, on a monitor that is Rec2020 or smaller, can very easily specify a completely wacky color that requires lasers to render, but they'll *see* a much more reasonable color on their screen, and they'll design against that more reasonable color they see, not what they *theoretically* specified. Ensuring that the color *stays* reasonable as monitor tech advances future-proofs the color, and eagerly mapping that into the rec2020 gamut accomplishes this. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9449#issuecomment-2162577936 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 June 2024 09:45:44 UTC