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

> jsbin supports HTTPS

Don't you have to pay for HTTPS support in JSbin? I don't think that invalidates the argument.

> That is totally browser specific stuff, and nothing to do with anything exposed as web APIs.

That's fair. Maybe it's just like that in Chrome because of the way they implement their elements. I think it still stands as a valid argument, though. It seems to me if standard HTML elements can work over HTTP that it's a double standard to not allow authors to create custom elements over HTTP.

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