[w3c/webcomponents] [Shadow]: return of multiple shadow roots? (#780)

Multiple shadow roots were removed as per https://github.com/w3c/webcomponents/issues/90, because Apple didn't want them and others were [happy](https://www.w3.org/wiki/Webapps/WebComponentsApril2015Meeting) to defer them to a later version of the spec.  Complexity aside, there were plenty of great things about multiple shadow roots, not least the ability to transparently attach multiple behaviours to an element without fear of collisions in styles, ids or other attributes.

Take the `<body>` element, for instance.  A 3rd-party library wants to add a positioned tooltip, another wants to add some popups, another some dialogues.  Maybe a browser addon wants to decorate parts of the body without interfering with a website.  Without multiple shadow roots, none of these parties can act transparently, with 100% certainty that they won't introduce side effects by adding elements and styles to the dom.  One of them could create a shadow root, but that prevents the others (or the page owner) from doing the same.  If each could own a shadow tree on the body, they could add their own stylesheets or manipulate elements with full confidence in the encapsulation.

Is there still vendor interest in returning nested shadow roots in the future?

-- 
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/780

Received on Monday, 7 January 2019 16:50:16 UTC