Re: [csswg-drafts] [css-nesting-1] Should prefixing nested selectors be mandatory? (#8270)

My understanding of the "require & prefix" idea is that & at the start only substitutes to `:is(parent-selector)` if it is the only & in the nested selector, otherwise it substitutes to nothing. So:

`section {
  & article  {
     ...
  }
}`
maps to `section article` while
`section {
  & article &  {
     ...
  }
}`
maps to `article section`
If you wanted `section article section` you'd have to write
`section {
  & & article &  {
     ...
  }
}`
which works mechanically, but to me feels very confusing.

And I agree that the Robustness principle should be the guide.

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


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

Received on Wednesday, 4 January 2023 14:55:22 UTC