- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Feb 2025 14:51:52 +0000
- To: public-css-archive@w3.org
cdoublev has just created a new issue for https://github.com/w3c/csswg-drafts:
== [css-syntax-3] Allow positioned {}-block in `@property/initial-value` ==
Per [spec](https://drafts.csswg.org/css-syntax-3/#consume-declaration), a positioned {}-block is allowed for a custom property, but not for `@property/initial-value`:
> 8. [...] Otherwise, if `decl`’s value contains a top-level simple block with an associated token of `<{-token>`, and also contains any other non-`<whitespace-token>` value, return nothing. **(That is, a top-level {}-block is only allowed as the entire value of a non-custom property.)**
A possible solution could be to apply this only *"if `decl`s name is a [supported CSS property](https://drafts.csswg.org/cssom-1/#supported-css-property)"*.
However, I think the intention of step 9 is to allow reparsing `a:hover {}` / avoid reparsing `--custom: var(1) {}`, as a qualified rule. But it indifferently returns *"nothing"*. So it could return an *"invalid declaration error"* instead. [Consume a block's contents](https://drafts.csswg.org/css-syntax-3/#consume-a-blocks-contents) would also need to be updated accordingly.
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11737 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 18 February 2025 14:51:53 UTC