Re: [w3c/webcomponents] Consider exposing Shadom DOM and Custom Elements only in secure contexts (#449)

On restricting Shadow DOM and Custom Elements to HTTPS:
* MS Edge position is not to restrict to Secure Context because
  * Web Components provides features that have been previously available without Web Components. they provide simplification of existing features using better architectural primitives and encapsulation.
  * Is a fundamental building block of the platform, and like the DOM Tree APIs, should be universally available.
  * Don’t believe that web components adds significant new privacy or security concerns to the web that would really justify considering it for secure context. 
  * While we like the adoption of HTTPS everywhere, I’m not certain that Web Component adoption and HTTPS adoption are linked or linkable. One should probably not block the other.

---
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/449#issuecomment-205531855