On 15/04/15 10:59, Anne van Kesteren wrote: > HTTPS already has mixed content, we should not make it worse.
What's actually wrong with mixed content? 1) The risk of content tampering. Subresource integrity makes that risk go away. 2) Reduced privacy. And that's why the connection would be marked as insecure in the UI. Gerv _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
