W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2010

[whatwg] Encrypted HTTP and related security concerns - make mixed content warnings accessible from JS?

From: Anne van Kesteren <annevk@opera.com>
Date: Sat, 13 Nov 2010 11:26:23 +0100
Message-ID: <op.vl3tx8f164w2qv@anne-van-kesterens-macbook-pro.local>
On Fri, 12 Nov 2010 23:02:16 +0100, Ingo Chao <i4chao at googlemail.com>  
> An event that says 'something was loaded insecurely' would be helpful.
> No need to report the URL, and no need to have the ability to prevent
> the loading in the first place.
> The bug reporting tool of the mashup page would inform me that the
> mixed content warning event was fired. These issues have to be
> investigated manually in any case.

Maybe this is something that should be warned for in the error console  
instead then? Why does this need to be an API exposed to the web?

Anne van Kesteren
Received on Saturday, 13 November 2010 02:26:23 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:28 UTC