- From: David Burns <notifications@github.com>
- Date: Mon, 19 Nov 2018 09:17:11 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 19 November 2018 17:17:32 UTC
> > @diervo So are all your shadow DOMs open. > > @jgraham, they could be open or closed, depending on some other boundaries (e.g.: is the child and parent from the same developer, or not). But that is irrelevant because we could bypass that by patching the `attachShadow()` mechanism to always store a reference of the shadowRoot somewhere, e.g..: `elm.__nakedShadow__`, so our `expandShadow` mechanism can use that instead of just `elm.shadowRoot` which is dictated by the `mode` configuration. We need to have something where we are not trying to run JS before something else could be. This approach, which is fine for now, will lead to a point where the atoms lose the race. We need a solution that never hits that situation. As for `expandShadow`, this is kind of along the same lines as my original PR for a "switch to shadow root`. We can change it to "getShadowRoot" or whatever really and then carry on from that point. It can easily be integrated into most peoples abstractions for their web application. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/771#issuecomment-439971456
Received on Monday, 19 November 2018 17:17:32 UTC