- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Thu, 23 Mar 2023 19:21:11 +0000
- To: public-css-archive@w3.org
> As I pointed out in the call, there is precedent for us making a change with similar dangers, when we moved from device RGB to sRGB. I don't recall anyone having text readability concerns then, and arguably that was an even more impactful change (since it also affected spot colors, not just transitions between them). Correct me if I am wrong, but the change from device RGB to sRGB was homogenous across any colors defined in CSS right? That change also made CSS defined colors more consistent and predictable overal. It made it easier to work with color on the web. This change however doesn't do any of that. It makes gradients more visually pleasing but authors can already opt-in to the those without breaking backwards compat. I don't think these two changes are actually similar in nature. ------- > This example is specifically crafted for this purpose, but how prominent is this problem in the wild The same is true for the inverse. Any examples in favor of this change are crafted to show visually pleasing gradients out of context. But it is the context that is the important part. It hasn't been demonstrated that authors want this change. -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7948#issuecomment-1481766758 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 23 March 2023 19:21:13 UTC