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

> Add to this the fact that, in order to protect the developer from themselves, we have to create an exemption in every third-party interface that should have access.
Nobody is forcing developers to close shadow trees.  It's entirely their choice.  If it causes them trouble, they can easily open them in the source code and forget all about closed shadow trees.  Alternatively, if they want to access closed shadow trees during testing, they can hook `attachShadow` quite easily as you pointed out in your opening post.  Likewise, any developers on the web can do this to explicitly gain access to a component and modify it.

I, for one, am very keen on closed shadow trees.  They're a safety mechanism on a footgun and they can provide comfort to developers that they can safely make changes to their components.  Taking the safety off _should_ be as inconvenient as it is, as developers who take the time to learn how to do it are likely to learn the risks in the process.

If you don't like the closed flag, simply don't use it.

---
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-218841481