- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 20 Oct 2023 18:15:54 +0000
- To: public-css-archive@w3.org
Actually, let me make this clearer: I will formally object to treating `& {...}` differently from `& .foo {...}`.
Happy to work on the issues via *some other mechanism* (like Anders says, wrapping them in a different kind of rule instead - let's re-re-revive `@nest`!), but I'm absolutely not ok with having different behavior based on the exact selector used.
Do we want to repurpose this thread to discussing how to solve the "naked property nesting inherits some of Nesting's weaknesses" issue, or open a fresh issue?
--
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9492#issuecomment-1773189683 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 20 October 2023 18:15:56 UTC