Re: [webcomponents] Consider exposing Shadom DOM and Custom Elements only in secure contexts (#449) from Anne van Kesteren on 2016-03-28 (public-webapps-github@w3.org from March 2016)

From: Anne van Kesteren <notifications@github.com>
Date: Mon, 28 Mar 2016 00:26:41 -0700
To: w3c/webcomponents <webcomponents@noreply.github.com>
Message-ID: <w3c/webcomponents/issues/449/202280674@github.com>

Relative URL resolution? It seems you're highly likely affected by that in some way.

I also don't really follow the concerns. The end goal is that insecure HTTP does not exist. Why does moving up the pace matter at this point, given all the infrastructure for HTTPS is now trivially available?

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

Received on Monday, 28 March 2016 07:27:09 UTC