- From: Guillaume via GitHub <noreply@w3.org>
- Date: Fri, 22 Aug 2025 07:37:57 +0000
- To: public-css-archive@w3.org
cdoublev has just submitted a new pull request for https://github.com/w3c/csswg-drafts: == [css-conditional-5] Use the generic <boolean-expr> == As a consequence of 5f19369, [`<boolean-condition>`](https://drafts.csswg.org/css-conditional-5/#typedef-boolean-condition) is extracted by `w3c/reffy` and exposed to `w3c/webref` users. However, `<boolean-condition>` was intended to be defined generically, as noted under its definition, and this has been done with [`<boolean-expr>`](https://drafts.csswg.org/css-values-5/#typedef-boolean-expr) in 4fd47d8 in CSS Values 5. Therefore this PR replaces `<boolean-condition>` with `<boolean-expr[ <if-test> ]>` in the prelude of `@when` and `@else`. The leaves of the boolean condition/expresion are consequently different: ```diff - media( [ <mf-plain> | <mf-boolean> | <mf-range> ] ) + media( <media-feature> | <media-condition> ) | - supports( <declaration> ) + supports( [ <ident> : <declaration-value> ] | <supports-condition> ) | + style( <style-query> ) ``` I assume these differences should not exist and will be fixed later if required, and that accepting `style()` queries is ok. See https://github.com/w3c/csswg-drafts/pull/12640 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 22 August 2025 07:37:59 UTC