- From: Guillaume via GitHub <noreply@w3.org>
- Date: Mon, 28 Jul 2025 09:40:51 +0000
- To: public-css-archive@w3.org
I am not sure this is actually a requirement, but it is at least a problem for [`w3c/reffy`](https://github.com/w3c/reffy/issues/1878#issuecomment-3113799544): `<boolean-expr-group>` is included in the production rule of `<boolean-expr[<test>]>` but it is not defined elsewhere. `<<boolean-expr-group>>` does not work in [`<xmp>`](https://github.com/w3c/csswg-drafts/blob/037dbfaab90986d2e546cf4631f65d21c504c3a5/css-values-5/Overview.bs#L258), which is presumably used instead of `<pre>` to avoid the Bikeshed error from the unrecognized grammar `<boolean-expr[<test>]> = ...`. Fwiw, `<boolean-expr> = ...` would make sense to me. I see `[<test>]` the same way as a numeric range in `<length-percentage [0,]>`. Relatedly, I do not quite understand the naming of `<boolean-expr-group>` from reading its production and the prose, which seems to be suggesting `<boolean-condition>` instead (emphasize added): > Several contexts [...] allow combining **those conditions** with boolean logic (and/or/not/grouping). > > ``` > <boolean-expr[ <test> ]> = not <boolean-expr-group> | ...` > <boolean-expr-group> = <test> | ( <boolean-expr[ <test> ]> ) | <general-enclosed> > ``` `<general-enclosed>` is unknown stuff. How does `<test>` represent a boolean expression group? -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10457#issuecomment-3126400963 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 28 July 2025 09:40:52 UTC