- From: Matthew Dean via GitHub <sysbot+gh@w3.org>
- Date: Sat, 07 Oct 2023 21:11:32 +0000
- To: public-css-archive@w3.org
Also... I thought the CSS Nesting spec specifically omitted as ident start for very good reasons of avoiding infinite ambiguity. Is there really a big problem just requiring this? ```css .foo { :is(div) {} } ``` or: ```css .foo { & div {} } ``` I don't understand the drive to create a new parsing / backtracking strategy and potentially break tooling to avoid typing `:is()` or `&`. What's driving this? -- GitHub Notification of comment by matthew-dean Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9317#issuecomment-1751818962 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 7 October 2023 21:11:34 UTC