- From: Jake Archibald via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Sep 2022 18:39:33 +0000
- To: public-css-archive@w3.org
> Did you mean references for script? Yeah, sorry, I wasn't clear. > For script access, we don't want to allow script to do everything that the Element API allows (like reparenting the element out of the shadow DOM). I think we could allow this. I'm assuming we could use the cascade to say the outgoing and incoming image elements don't 'work' outside of the shadow DOM. > I did want WA-API to be available to script in the initial version of this feature. And it looks like you can't target an element in a shadow DOM using the ::part selector with pseudoElement option Oof, yeah, that's bad. It's an important part of the feature. I wonder if there's a good reason it doesn't work, and if it'd also cause issues with a `CSSPseudoElement` reference. > The Scoped transitions aspect is what makes shadow DOM dealbreaker for me. +1 > > I suggested that the shadow root be attached to a pseudo-element > > This is a road I don't want to go down. It gets really weird if a pseudo-element becomes an ancestor for real elements. Yeah, I imagine there are a lot of reasons why it's a bad idea. -- GitHub Notification of comment by jakearchibald Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7743#issuecomment-1248466250 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 15 September 2022 18:39:35 UTC