Mixed content warnings are often hard to debug, since the insecure content is buried in some obscure stylesheet or iframe. By logging information about a mixed content event as a console warning, we can make removing mixed content easier for site developers. The most important pieces of information that we can log are the URL of the page that's attempting to include insecure content, and the URL of the content. I'm not sure if the console message type should be error or warning, but I'm leaning towards warning. Chrome used a warning before the mixed content detection was moved into WebKit.
Created attachment 41009 [details] patch I ran the existing mixed content http tests and they passed.
Comment on attachment 41009 [details] patch Thanks Collin!
Comment on attachment 41009 [details] patch Clearing flags on attachment: 41009 Committed r49431: <http://trac.webkit.org/changeset/49431>
All reviewed patches have been landed. Closing bug.