- From: Hayato Ito <notifications@github.com>
- Date: Wed, 03 Feb 2016 19:26:38 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Thursday, 4 February 2016 03:27:09 UTC
Thank you for the feedback. Hmm. The original motivation of introducing a closed shadow tree is "Never allow an access to a node in a closed shadow tree, via any APIs, from outside", AFAIK. In fact, I designed a closed shadow tree in such a way. If there is a way to access a node in a closed shadow tree, it should be considered as a *bug* in the spec. I think it's totally okay to have an API to allow an access in Chrome apps or extensions level. However, for a *normal* web app, I think the current agreement is "Never allow it". If we allowed it, that means we do not need a closed shadow tree. Just having an open shadow tree is enough, I think. See also https://github.com/w3c/webcomponents/issues/354. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/378#issuecomment-179596975
Received on Thursday, 4 February 2016 03:27:09 UTC