- From: Hayato Ito <notifications@github.com>
- Date: Sun, 17 Apr 2016 22:07:25 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Monday, 18 April 2016 05:09:42 UTC
Thank you, @annevk , @smaug---- . Blink is fine with 1 in https://github.com/w3c/webcomponents/issues/184#issuecomment-210321856. Shadow DOM is originally designed to provide an encapsulation for DOM tree structures. It was not designed to provide an encapsulation for scripts. Thus, as long as nodes in a shadow tree are not leaked to outer trees, I am okay. A *behavior leakage* (I am not sure how I can call this..) which would be caused by scripts is not what I expect Shadow DOM to prevent that. I do not want Shadow DOM to own such a role magically beyond its original role. It would be nice that we could have a separate primitive which prevents these kinds of influences from happening, other than *reusing* a boundary provided by Shadow DOM. A unit of a shadow tree and a unit of joint session history does not have to be the same, I guess. --- 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/184#issuecomment-211204354
Received on Monday, 18 April 2016 05:09:42 UTC