Re: [w3ctag/design-reviews] CSS if() function (Issue #1045)

I'm biased because this was my proposal, but this is solving a host of huge author pain points, and together with style queries, can enable higher level custom properties which will make web component APIs a lot more fluent. The `style()` syntax is not ideal ergonomics, but it was chosen for consistency with style container queries and there are plans to expand it to regular value comparisons down the line.

The explainer examples could be better though. Comparison with color values is not the common case at all, and is rather hairy. The common case is probably a keyword valued custom property like `--variant: success | warning | danger | neutral | primary` and seeing how it can be used to set multiple other properties.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1045#issuecomment-2626913361
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1045/2626913361@github.com>