- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Apr 2025 14:49:57 +0000
- To: public-css-archive@w3.org
I think some of the things I said weren't quite minuted. But the issue here is that, given if shadow dom and light dom rules are stored separately (which is useful for a lot of reasons): * Changes in the light dom need to somehow go look at the shadow root of an arbitrary ancestor (or not even ancestor, see next comment), in order to find the `:has()` rules. * Inserting a shadow host becomes very non-local, specially if we allow combinators like `:host(:has( ~ foo))` or so, suddenly it affects arbitrary elements on their following siblings and sibling-descendants etc. -- GitHub Notification of comment by emilio Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11859#issuecomment-2776052317 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 April 2025 14:49:58 UTC