- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Feb 2022 19:21:58 +0000
- To: public-css-archive@w3.org
I'm fine with disallowing nesting. We've done similar in other non-selector cases to limit complexity. There are definitely use-cases for it, but they're indeed minimal. If at all possible I'd like to avoid disallowing the other selectors, even if the perf isn't ideal. We have much better tools these days to expose and analyze selector performance than we did a decade ago. I presume this means that nested :has() is disallowed even when "shielded" by another selector, like `:has(:not(:has(.foo)))`, right? -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6952#issuecomment-1030281380 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 4 February 2022 19:22:00 UTC