- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Dec 2022 18:57:33 +0000
- To: public-css-archive@w3.org
And for the record, there was also already some discussion earlier about requiring `&` at the beginning of every nested selector. This avoids lookaheads entirely but also burdens writing nested selectors.
And before somebody asks, `.foo & {...` would be expressed as `& .foo & {...` in that case.
(Note that I don't advocate for that syntax, I just wanted to mention it again, as it seems people forgot about the options that were previously discussed.
Though I am with @Loirooriol here and would always prepend my nested selectors with `&`. And I'd generally avoid putting `&` in the middle of a selector as that rather confuses than helps, IMO.)
Sebastian
--
GitHub Notification of comment by SebastianZ
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8248#issuecomment-1364209503 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 23 December 2022 18:57:34 UTC