- From: Peter Linss via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Apr 2023 21:46:53 +0000
- To: public-css-archive@w3.org
> This is not the case. Unrecognized rules will stop at the end of the rule (the }), so a following declaration (or rule) will be parsed as normal.
That might be true in a browser that implements nesting, and manages to detect the rule as a rule and not fall back to treating it as a declaration.
Try this in a browser that doesn't support nesting:
```html
<style>
p {
color: red;
span { color: yellow; }
color: green;
}
</style>
<p>This should be GREEN</p>
```
or this in a browser that does:
```html
<style>
p {
color: red;
custom-element:unknown { color: yellow; }
color: green;
}
</style>
<p>This should be GREEN</p>
```
(and if that works, imagine `custom-element` conflicts with a future property name)
--
GitHub Notification of comment by plinss
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8249#issuecomment-1498200267 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 5 April 2023 21:46:54 UTC