- From: Peter Linss via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Dec 2022 01:42:15 +0000
- To: public-css-archive@w3.org
> As an author, I would be strongly against something that requires me to create a whole separate rule like that. Part of the benefit of nesting is organizing my code into portable "chunks", so I can copy a rule and have all the CSS needed for a "component". It seems that option 5 breaks this, unless I'm missing how exactly it's supposed to be used. I don't understand your point here at all. All the CSS for a "component" is within the @nest rule and it can be copied as a whole. If anything, by not requiring `&` everywhere you're making your CSS more copyable and usable in other contexts. Can you give an example of what you';re concerned about? (and how that would be different from the other proposals) -- GitHub Notification of comment by plinss Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7970#issuecomment-1333028694 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 1 December 2022 01:42:18 UTC