- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Mon, 02 Mar 2026 22:36:08 +0000
- To: public-css-archive@w3.org
Yeah, part of this was that CSS has had a "type selector must go first" requirement since forever. We temporarily violated that with `&` when it was required to quickly recognize a nesting rule, but after the parsing fixes that was no longer required, so we returned to type selector, when specified, being first. It also happened to be convenient for Sass, since `&bar` was the biggest case where Sass's nesting and CSS's nesting would significantly diverge in behavior. `bar&` works the same in both, so if we required it in CSS it would be helpful for their migration tools. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10523#issuecomment-3987350580 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 2 March 2026 22:36:09 UTC