Re: [csswg-drafts] [css-color-5] `light-dark()` should resolve at used value time, not computed value time (#13836)

> Is this desirable? I suspect it will complicate implementations in a way that is similar and possibly even worse than currentColor, looking forward to hearing from implementors! cc @emilio @weinig(not sure which Blink implementor is working on color but hopefully @andruud or @tabatkins know?)

I don't have a strong take on the desirability of this behavior, but I think @Emilio is probably right that this seems like an issue that is a "larger-scope problem than light-dark". 

From an implementation standpoint, however, I don't think changing light-dark() to resolve at use time would be that big a burden on the engine (at least for WebKit, I can't speak to the other engines). It is actually because of currentColor, that we already explicitly resolve "used" colors already. Adding something else that might need to be resolved at those times would not be a big issue.

-- 
GitHub Notification of comment by weinig
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13836#issuecomment-4320092250 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Saturday, 25 April 2026 16:43:09 UTC