- From: S H via GitHub <noreply@w3.org>
- Date: Wed, 01 Oct 2025 17:15:36 +0000
- To: public-css-archive@w3.org
I think I see this mentioned early on but it seems to have been left behind or I'm overlooking the explanation for why it doesn't matter. What's the consideration for use cases where visual accuracy is not primary intent? That is, outside of the photagraphic space, where intelligibility trumps accuracy? As a practical example, suppose I have a reference colour and I want to add a colour tint to it to make it visually distinct from other things of the same colour. Maybe I try something like `oklch(from currentColor l .3 270deg)`. If `currentColor` is black or white then my tint will have no effect. The "best" approximation dictates that lightness is preserved and saturation can be reduced but not increased. I have to hack around with `oklch(from currentColor clamp(.2, l, .8) .3 270deg)`, or something like that, to ensure that I get at least a little saturation; but I'm just hacking at that point, no longer expressing my intent. Just as a hypothetical (ignoring that it's nonsense syntax), what if I wrote `oklch(from currentColor l .3 !important 270deg)`? Then the implication would be that saturation should take precedence over lightness, so if we have to brighten or dim the colour in order to achieve visible hue then do that. -- GitHub Notification of comment by sh1boot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9449#issuecomment-3357342806 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 1 October 2025 17:15:37 UTC