- From: Tim Nguyen via GitHub <sysbot+gh@w3.org>
- Date: Mon, 07 Apr 2025 07:33:27 +0000
- To: public-css-archive@w3.org
Not convinced we should do the selector counterpart of this fyi, I don't really see any convincing use cases. It doesn't address the scoping use case either fwiw. > As we progress into CSS @function, if() and other checks, it seems that we'll eventually need a <boolean> type) CSS has no concept of coercing CSS values into booleans right now. All the current booleans are either selectors, numerical or equality comparisons. -- GitHub Notification of comment by nt1m Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7869#issuecomment-2782297069 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 7 April 2025 07:33:28 UTC