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

I don't think we want to change the HTML parser behavior based on the protocol if we were to resolve the issue #59 in favor of the parsing `slot` element like `template` element.

Also, while features like geolocation and service workers can be progressive enhancements to a given web page / app, web components seems like a fundamental bundling block of the said page / app, and not having them would force them to use polyfill instead of degrading user experience.  So imposing secure origin seems unusually hostile requirement to me.

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