- From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
- Date: Tue, 17 Mar 2015 12:42:44 -0400
- To: Mike West <mkwst@google.com>, Peter Eckersley <pde@eff.org>
- Cc: "public-webappsec\@w3.org" <public-webappsec@w3.org>, Eric Mill <eric@konklone.com>
On Mon 2015-03-16 05:26:39 -0400, Mike West wrote: > Optionally-blockable mixed content is certainly also an important issue, > though, as it creates UI degradation, which developers very much wish to > avoid (as noted in #2 in the email you're responding to). If Chrome provides degraded UI for plain http:// sites (i think this has been discussed recently, but don't have a link handy), then the site operators will have only one way to fix this, which is a move to full HTTPS with mixed content at all, right? --dkg
Received on Tuesday, 17 March 2015 16:43:23 UTC