- From: Devon Govett via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Oct 2022 20:09:24 +0000
- To: public-css-archive@w3.org
> Instead, that . would cause us to attempt to "parse an ambiguous rule", and when we hit the ; we'd realize it was instead an invalid property all along and just drop it, without changing the parsing mode.
Ah, I missed this detail, thanks. This does have the downside that a semicolon after a nested rule means that rule is thrown away. Could trip people up.
```css
.foo {
.bar { color: red }; /* not applied. remove the semicolon and it works! */
}
```
--
GitHub Notification of comment by devongovett
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7834#issuecomment-1275216747 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 October 2022 20:09:25 UTC