Re: [w3c/webcomponents] Shadow tree encapsulation and Element Timing (#816)

> Can you explain why it breaks encapsulation? If the flag is passed, the component author has agreed to expose the performance information.

Because it leaks nodes inside a shadow tree. In general, we don't provide that kind of opt-in. Opt-in we have deciding whether `shadowRoot` is exposed or not, and whether `Event.composedPath` would contain nodes inside the shadow tree or not. Note that in both cases, the users of the API is explicitly accessing the shadow DOM related API. There is no chance of nodes inside a shadow tree suddenly appearing in an existing API such that existing code can stumble upon them. That literally is the whole point of shadow DOM API.

-- 
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/816#issuecomment-500570912