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

> The end goal is that insecure HTTP does not exist.

But not for web components. This is conflating two completely separate issues.

> Why does moving up the pace matter at this point, given all the infrastructure for HTTPS is now trivially available?

As time goes on, the web component spec seems to be losing a lot of steam in the community. I have seen far more skeptics than advocates for web components at work, meetups and on the internet without basing what I read on my personal bias. It's just as much conjecture for one to argue that this will help with HTTPS adoption as I would argue that it will hurt adoption of the spec and how it is portrayed within the community.

If we take out the HTTPS agenda, what is this actually solving?

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