Re: [csswg-drafts] [css-nesting-1] Wrapping parent selectors with `:is()` introduces a host of problems (#9492)

> Did the non-@nest solution for keeping nested declarations in-order help solve this?

No, not entirely

Implementations can now make this example work as expected:

```css
::before, ::after {
  @media screen {
    /* used to be an implicit `& {}` */
    content: "hello";
  }
}
```

But this still won't work:


```css
::before, ::after {
  @media screen {
    &:hover { /* explicit rule containing `&` */
      content: "hello";
    }
  }
}
```

The only thing that has been solved is that at rules like `@media` or `@starting-style` can now contain declarations without needing to generate an implicit `& {}` rule.

That `&` is _equivalent_ to `:is()` and that `:is()` can't contain pseudo elements hasn't been solved.

So it became even more nuanced in what does and does not work.

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


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

Received on Wednesday, 10 July 2024 07:08:32 UTC