- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Tue, 21 Oct 2025 17:14:22 +0000
- To: public-css-archive@w3.org
Yup, what you're missing is our general decision to make any of the boolean grammars conform to "particles are always parenthesized or functions", so we can actually define `<general-enclosed>` (the catch-all error term in the `<boolean>` grammar) in a way that lets us parse in a forwards-compatible fashion. If the tests could be *anything*, we'd have no way to know where `<general-enclosed>` should end, so we'd have to fail parsing the entire tree when we encountered anything unknown. See <https://www.w3.org/TR/css-values-5/#typedef-boolean-expr> and <https://www.w3.org/TR/mediaqueries-5/#typedef-general-enclosed> -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12997#issuecomment-3427945044 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 21 October 2025 17:14:23 UTC