- From: Isaac Muse via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 Mar 2024 03:03:11 +0000
- To: public-css-archive@w3.org
> I wonder if it may make sense to give authors control over what is preserved, lightness, colorfulness, or hue. The issue is that thinking about use cases, there are cases where you want to tie that to the _color_ (e.g. creating tints of a primary color) and cases where you want to tie that to the element, but adding both a functional notation (or color function keyword) AND a new property seems overkill. By no means am I arguing for CSS to support multiple approaches. I am more acknowledging that there are benefits to either lightness preservation or chroma preservation, but there are also weaknesses. One could even argue that you could find some middle ground between the two. I think there will be people in either camp, all with valid reasons, and sure it may be nice to have access to all possible options to account for all use cases, but that may not even be practical. I really wanted to highlight that there is no perfect way. No matter what you do, you are sacrificing something to gain something else. Whether it's good contrast, or gamut mapped colors do not appear as colorful as they really are, etc. There will be a trade-off no matter what. Even if you take a middle path, something is sacrificed. Really, we need "something". Without some form of gamut mapping, all the new color stuff is crippled. I think knowing what you get and what you don't get with various methods helps. I think what really needs to be decided is what do authors want most? What do they find to be the most important? I think whatever the solution is, it should answer that question. If you can only do one thing, it should address the most important issues. -- GitHub Notification of comment by facelessuser Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9449#issuecomment-1998856601 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 15 March 2024 03:03:12 UTC