- From: Westbrook Johnson via GitHub <sysbot+gh@w3.org>
- Date: Mon, 26 Aug 2024 12:01:56 +0000
- To: public-css-archive@w3.org
I would say that the `compound-selector` restriction on `:host()` should be removed all together, rather than attempting to add extra nuance to it in these cases (e.g. `:host(:has(div))`, `:host(.a:has(div))`, `:host(.a:has(> div))`, `:host(:is(div .a)`, `:host(:is(div > .a)`, et al). These are are important selecting contexts that shouldn't be removed from a developers tool box just because they chose to leverage shadow DOM as their encapsulation method rather than something like `@scope`. I would go further to day that this restriction and the same on `::slotted()` are based on performance data from more than 10 years ago when no browsers was shipping `:has()` or container queries (both, also, for their performance constrains). That's multiple epochs in frontend development, and 100+ major versions in various browsing engines. It would be a really interesting addition to this conversation to be able to see updated numbers on whether the costs here continue to warrant the need for these restrictions in the more modern architectures by which browsers power selector parsing today. -- GitHub Notification of comment by Westbrook Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10756#issuecomment-2310038306 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 26 August 2024 12:01:57 UTC