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

I think we can agree that there is no technical reason to restrict Shadow DOM or Custom Elements to HTTPS. DOM (or Shadow DOM) can work the same way either in HTTP or HTTPS, basically.

> Just for the sake of exposing new major APIs to secure context only to persuade web devs to give up with less secure contexts.

Thus, I think the point is that motivation is important enough or not.

---
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-199622963