- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Apr 2023 21:46:02 +0000
- To: public-css-archive@w3.org
Right, I argued in previous discussions that forbidding decls after rules is fundamentally problematic. The basic question is "when has a rule occurred?", and this needs to *not* be dependent on whether a rule is valid or not, as that would mean different browser levels would interpret following properties differently.
So you need to define some notion of when we've found a rule, that allows for invalid rules, and do so in a way that doesn't unduly restrict our future syntax options.
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?
------
On the other hand, sticking with the current design that just allows them, and relying on people to not write unreadable stylesheets, suffers from none of these issues.
--
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8738#issuecomment-1515426686 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 19 April 2023 21:46:04 UTC