- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Oct 2022 19:18:06 +0000
- To: public-css-archive@w3.org
I'm confused. If when the structure is ambiguous you definitely parse as a declaration, that means `fieldset & {...}` will just be an invalid declaration, rather than a rule, which doesn't seem to be what you're suggesting. That's just the existing Option 3.
If you mean "parse as a declaration but also do X to allow for reinterpreting as a rule later", then it is indeed a per-declaration cost to do X.
> But since these are invalid we throw them away anyway, no?
Yeah, but today we throw them away as an *immediate* error-handling consequence - we see the `*` and just switch into "consume tokens until we see a semicolon" mode immediately without creating any additional data structures. With Nesting we'll start making a rule object on the *assumption* that it's gonna turn out to be a valid rule, and then later throw that out when it ends up being an invalid declaration; that's an extra cost. (Just a rare one.)
--
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7961#issuecomment-1292515397 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 October 2022 19:18:08 UTC