- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Fri, 19 May 2023 12:12:51 +0000
- To: public-css-archive@w3.org
> Please don't delete your comments, it's very confusing reading an email, coming here to answer the questions, and finding there's no comment anymore. Sorry about that. My intent was to avoid hijacking the thread with a minor mistake and something I was wrong about, indeed. --- `<declaration-at-rule-list>` is perhaps clearer than `<declaration-rule-list>`: > `<declaration-rule-list>`: declarations and at-rules are allowed; qualified-rules are automatically invalid. ...and more consistent with `<at-rule-list>`. --- A link to *consume a block's contents* in the description of `<block-contents>` and its subproductions might also be usefull, perhaps in this [paragraph](https://drafts.csswg.org/css-syntax-3/#block-contents): > The CSS parser is agnostic as to the contents of blocks—they’re all parsed with **the same algorithm**, and differentiate themselves solely by what constructs are valid. --- > **[5.4.5. Parse a list of declarations](https://drafts.csswg.org/css-syntax-3/#parse-block-contents)** > > To **parse a block’s contents** from input: I think it should be *"To **parse a list of declarations** from input:"*. -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8834#issuecomment-1554481507 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 19 May 2023 12:12:53 UTC