Re: [csswg-drafts] [css-nesting] Problems with indiscriminately wrapping all parent selectors with `:is()` (#9492)

And just to keep adding to the summary, I think the "explode by specificity" that @LeaVerou proposed would work along these lines:

```css
article, .article {
    color: red;
    @mixin something;
    color: green;
}
```
can be rewritten
```css
article, .article {
    color: red;
    @mixin something;
    :where(&):is(article), :where(&):is(.article) { color: green; }
}
```

Note that, even though it might be undesirable in the general case (no strong opinion on this), it's possible to do this rewriting only in the case of "promoted" declarations where wrapping `& {}` would result in wrong specificity for the declaration after promotion.

I would personally be fine with something like this being done only for the rare case of out-of-order declarations. But this begs the question whether this should be the default indeed. I think implementors should give it some thought. It might not be as difficult as it looks like.

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


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

Received on Wednesday, 25 October 2023 17:10:57 UTC