- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Apr 2023 19:49:43 +0000
- To: public-css-archive@w3.org
> For example, if we ever allow {} in a property, and you write it invalidly so it triggers rule parsing, would that kick the "now there's a rule" switch? Does that mean we actually have to _forbid_ ever using `{}` in properties?
If you mean the _property value_ and I interpret the algorithm correctly, then `{}` is already allowed by consuming a [component value](https://drafts.csswg.org/css-syntax-3/#consume-a-component-value) in step 5 of [consuming a declaration](https://drafts.csswg.org/css-syntax-3/#consume-a-declaration). And it can't trigger rule parsing because the consumed component value is appended to the declaration's value.
Sebastian
--
GitHub Notification of comment by SebastianZ
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8738#issuecomment-1526293624 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 April 2023 19:49:44 UTC