- From: Hayato Ito <notifications@github.com>
- Date: Tue, 16 Feb 2016 08:18:09 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Tuesday, 16 February 2016 16:18:42 UTC
The basic rule should be: - Do not leak any node, name or anything else about a shadow tree via any *existing* APIs. We do not want developers to access shadow trees unintentionally. - It's okay to access a node in an open shadow tree via *new* API, e.g. `Element.shadowRoot`, `Element.getAssingedSlot`, `Event.deepPath()`, because there is an explicit intention. - Never allow to access a closed shadow tree, even when an author uses a new API. e.g. `Element.shadowRoot` should return null for a closed shadow tree. We might want to judge case by case carefully, however, we should honer this basic rule as possible as we can. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/145#issuecomment-184751329
Received on Tuesday, 16 February 2016 16:18:42 UTC