Re: [w3c/webcomponents] Alternative proposal for closed shadow DOM (#499)

> Doesn't seem to be much discussion of this or any planned fixes on the Chrome side. Could you link me if I've missed it?

Such discussion has to happen at each browser vendor and/or for the [WebDriver specification](https://w3c.github.io/webdriver/webdriver-spec.html), not here.

> Not to mention that a developer might want to create intentional dependencies on the internals of shadow trees, regardless of whether the component author intended for them to.

This is precisely why closed shadow tree is needed.  Because of this possibility, once a component is published and used by third parties, there is no way for component authors to know whether there is any use of the component that depends on a particular shape of its shadow tree.  Closed shadow mode makes it much likely that this would not happen.

---
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/499#issuecomment-218668286