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.

I admit I'm not familiar with JSBin, and I was pretty dismayed to discover that, they supports HTTPS just fine, they just **turn it off** for the JS you type in.  I don't think rent-seeking behavior should really be a guide to decision-making here.  

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