- From: Jeffrey Yasskin via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 Apr 2024 23:19:06 +0000
- To: public-css-archive@w3.org
@romainmenke I'm not arguing against a better gamut mapping algorithm than clipping, and neither is @ccameron-chromium at this point. The question is what kind of gamut mapping to pick. I agree that we likely need to give authors more control, although as @LeaVerou pointed out, we do also have to pick a default. I can't say for sure exactly what Chrome's implementation constraints are, since I'm not @ccameron-chromium. The biggest one, though, seems to be that the same mapping algorithm has to produce good results for both images and CSS colors. He's also said that the problem space is novel and unknown enough that CSS shouldn't mandate a particular algorithm, but rather set a goal for implementations to meet. (E.g. "find the perceptually closest color of the same hue", probably within some error bound.) I'm not certain that's correct in the medium-term, but I am concerned by seeing folks talk about particular algorithms _before_ defining the goals those algorithms are meant to achieve. It could make sense to agree on some goals, watch what implementations do, and then try to align the exact results later. -- GitHub Notification of comment by jyasskin Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9449#issuecomment-2035796081 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 3 April 2024 23:19:07 UTC