Re: [whatwg/dom] Declarative Shadow DOM (#831)

Shadow DOM (or its closedness) is not a security boundary, but is - I suppose - provided for encapsulation, such that your users are discouraged from depending on you implementation details. Even if it were a security boundary, the articles you mentioned basically monkey patch the JS API before it's used - hardly a useful "bypass" in the context of this feature. It might be a bit off-topic to discuss changing the WebComponents API with its shadow DOM. 

Practically, it's possibly impossible to "un-ship" it years after the fact (it in every browser apart from IE, and possibly used a lot), and personally I don't think it matters much for the issue at hand, nor would I advocate the Shadow DOM.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/831#issuecomment-717796936