- From: flachware via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Feb 2022 17:37:13 +0000
- To: public-css-archive@w3.org
Thanks to you all for thinking this through! Just to clarify, this issue is not about deep nesting, it’s about nesting by itself. It strikes me that `@nest &` is considered to be a given, but `&()` is considered to be more advanced. I think it’s not, except that it is harder to come up with a syntax for it. Yes, there are workarounds, but that’s the whole point of the issue: the nesting mechanism should be powerful enough to be able to handle all possible combinations in a straightforward, readable, and DRY way – without the need to resort to custom properties etc. Assuming you write the following in a nested way: ```.foo .bar``` Then the nesting spec should be able to handle the following situations: ``` :hover .foo .bar .foo:hover .bar .foo :hover .bar .foo .bar:hover ``` None of these situations is more basic or more important than the others, some of them are just easier to represent in a nested way. But all of them exist and should be handled properly. -- GitHub Notification of comment by flachware Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6330#issuecomment-1030204929 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 4 February 2022 17:37:15 UTC