Re: [csswg-drafts] [css-cascade] [css-nesting] Figure out whether we're fine with "shifting up" bare declarations after rules (#8738)

Just pointing out that pseudo-elements aren't the only problem, there is also #9806

```html
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<style>
/*<![CDATA[*/
@namespace url("http://example.com/foo");
@namespace svg url("http://www.w3.org/2000/svg");
svg|svg {
  background: red;
  & * { --foo: bar; }
  background: green;
}
/*]]>*/
</style> 
<svg id="svg" width="100" viewBox="0 0 100 100" xmlns="http://www.w3.org/2000/svg"></svg>
</html>
```

This is currently green in browsers. But if we convert it into

```css
svg|svg {
  background: red;
  & * { --foo: bar; }
  & { background: green; }
}
```

then it's red, because `&` is not a type selector so it can only match in the default namespace, and our element is in the svg namespace.

-- 
GitHub Notification of comment by Loirooriol
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8738#issuecomment-1895805778 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 17 January 2024 13:23:54 UTC