- From: Gérard Mathiuet via GitHub <sysbot+gh@w3.org>
- Date: Fri, 19 Aug 2022 16:24:49 +0000
- To: public-css-archive@w3.org
@chee If I understood everything correctly, all you need to know about `@nest` (first variant) is that the notation known from SCSS comes into play, except when the nested element is a parent of it (e.g. styling an element based on if a dialog is open: `html:has(dialog[open])`). So there is not much to learn. Whereas `@nest always` feels extremely verbose to me, and depending on the codebase, could blow everything up quite a bit. `brackets`, on the other hand, increases indentation by one compared to the other two. **TL;DR**: 1. `@nest` = minmal, concise, with the possibility of using `@nest` for parent selectors 2. `@nest always/restricted` = verbose, tends to bloat the codebase 3. `brackets` = increases indentation by 1 -- GitHub Notification of comment by scherii Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4748#issuecomment-1220864544 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 19 August 2022 16:24:50 UTC