Re: [csswg-drafts] [css-nesting-1] Syntax Invites Errors (#7834)

> There are a lot of assumptions and personal opinions being thrown around here. Your own poll showed that developers prefer to write the `&` in every selector: [twitter.com/leaverou/status/1579902585540345857](https://twitter.com/leaverou/status/1579902585540345857). Yet this was pushed through anyway. It does not seem like feedback is being taken seriously, both from implementors and from authors.

This has already been addressed, I think by @fantasai: The poll showed that about half of developers (52%) want to include `&` in every selector, and half (48%) do not. Making it optional caters to both; the first group can *still* include `&` in every selector. Making it mandatory only caters to one of the two groups.

Also, if you read the comments, there was some confusion about what an optional `&` would be, many assumed it would be optional in _every_ case, including things like `&.foo`, `&:hover`, `.foo &` etc and wanted to change their vote when they realized that was not the case. This was clarified in the [subsequent poll](https://twitter.com/LeaVerou/status/1580215877705687040).

I understand that you feel strongly about this, but right now none of the proposals considered by the group involves a mandatory `&`, so this is not a productive debate, and I'm not going to engage in it further. Perhaps we can agree that if `&` is optional, it's better if it's optional in every case where selectors begin with `&` and a combinator? (I do not think it's so much better that it's warrants moving to a postfix syntax, but if we could get it to be optional in every case *and* keep a nested syntax, that would be ideal).

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


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

Received on Thursday, 3 November 2022 17:14:54 UTC