- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 01 Jul 2022 17:49:30 +0000
- To: public-css-archive@w3.org
The Syntax spec [is clear on this](https://drafts.csswg.org/css-syntax/#declaration-rule-list): > For rules that use [<style-block>](https://drafts.csswg.org/css-syntax/#typedef-style-block) or [<declaration-list>](https://drafts.csswg.org/css-syntax/#typedef-declaration-list), the spec for the rule must define which properties, descriptors, and/or at-rules are valid inside the rule; this may be as simple as saying "The @foo rule accepts the properties/descriptors defined in this specification/section.", and extension specs may simply say "The @foo rule additionally accepts the following properties/descriptors.". Any declarations or at-rules found inside the block that are not defined as valid must be removed from the rule’s value. > [...] > For rules that use [<rule-list>](https://drafts.csswg.org/css-syntax/#typedef-rule-list), the spec for the rule must define what types of rules are valid inside the rule, same as [<declaration-list>](https://drafts.csswg.org/css-syntax/#typedef-declaration-list), and unrecognized rules must similarly be removed from the rule’s value. So, unless otherwise explicitly stated, unknown/invalid descriptors, properties, or at-rules encountered in any at-rule do *not* invalidate the whole rule. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5109#issuecomment-1172580111 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 1 July 2022 17:49:32 UTC