Yeah, that won't happen when the rule is parsed (the first {} will end up being the body), but if you manipulate such a rule via the OM you can produce a rule that can't be serialized back out. So I support explicitly disallowing those. (We could theoretically still allow {} in the prelude of a body-less at-rule like @import, but that would prevent extension to a body-full rule later, and would just be a confusing sort of thing to allow.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5766#issuecomment-740195350 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Monday, 7 December 2020 21:38:17 UTC
This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:23 UTC