- From: Joseph Orbegoso Pea <notifications@github.com>
- Date: Wed, 14 Jun 2017 08:50:32 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 14 June 2017 15:51:36 UTC
I can see how multiple-shadow-dom fails, because it will change completely how the component works, and may just completely break everything. In other words, an extending author would have to replicate internal functionality, not just add custom functionality, and that may be super complicated (especially for a 3D rendering component, for example). I will be experimenting in this area, because the custom elements I'm making at [`infamous`](http://github.com/trusktr/infamous) are having WebGL rendering soon where the canvas is hidden in the shadow dom, and may also have a translation from nested DOM hierarchy outside of the shadow dom to an internal flat DOM inside the shadow dom for CSS 3D rendering without `preserve-3d`. So I will post back any patterns I may find. -- 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/643#issuecomment-308474714
Received on Wednesday, 14 June 2017 15:51:36 UTC