Re: [csswg-drafts] [css-nesting] & rules (#6119)

> Yup, that's how Selectors normally work. ^_^ For example:

I was not talking about selectors, I was talking about a something that is not yet in the language?

> This ambiguity can persist indefinitely, until you see a ; or {; (because the parent rule closes with a }, for example), it might not be possible at all to tell which was intended.

Well, by indefinitely you mean until the next char or line where the parent closes with `}`? 

But even if that was a problem, instead of solving that (forcing the last property of a block to use semi-colon), we introduce 2 new things,  one `&`, and one `@nest` to solve the readability of the first to be introduced? And on the `@nest` you still have to use the ampersand.

Since I can use preprocessors I will do that and not insist on this, it's clear it's something that's going to go anyway and not up to discussion.

```
div {
    &.class_1 { }
    & class_2 {}
    &.class_2 {}
}
``` 

Over this

```
div {
    &.class_1 {}
    .class_2 {}
    &.class_2 {}
}
```



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


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

Received on Saturday, 20 March 2021 04:11:47 UTC