- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Mar 2024 14:14:06 +0000
- To: public-css-archive@w3.org
@ccameron-chromium said: > Yes, this is true. No matter what we do with this sort of input, it's going to be "wrong" by some definition, and clipping is just a "simple wrong". And it's also very hard to identify what input is intentional versus unintentional. > > This is why I hope that we can put effort into enabling a safe parameter space (be that `okhsl`, or some built-in guardrails for `oklch`). If we fix that problem, then users can take advantage of the nice features of things like relative color syntax, without running this risk. These are not mutually exclusive. We can put effort into designing better color spaces for color manipulation AND implementing a decent GMA, which will be needed *regardless*. You're already clipping, so I don't understand what the reasoning is to not do better. It doesn't stop you from designing new color spaces. The algorithms are already there, just tell us what the performance constraints are and we can get you one that maximizes quality while fitting within them. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9449#issuecomment-2025286573 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 28 March 2024 14:14:07 UTC