Hi DavidR,

Google announced that it is going to block HTTP-content on HTTPS-sites: http://googleonlinesecurity.blogspot.com/2011/06/trying-to-end-mixed-scripting.html
link from Google Online Security Blog, authors Chris Evans and Tom Sepez, Google Security Team,
From then on it is going to look like (png link taken from same source)
http://3.bp.blogspot.com/-DO9bA_NOFjQ/TfqIpU7Zb8I/AAAAAAAAIJI/ePLB8p3algc/s1600/blocked%2B%25281%2529.png

IE9 is also going to protect against mixed content: http://blogs.msdn.com/b/ie/archive/2011/06/23/internet-explorer-9-security-part-4-protecting-consumers-from-malicious-mixed-content.aspx IEblog 16 author Eric Lawrence
Program Manager

Chrome tracks mixed scripting more precisely than Firefox or IE (as seen from the attachment in my previous posting) Here the user can install the Mixed content protection extension:
http://userscripts.org/scripts/source/69977.user.js (only works for the body tag elements)
Because of this thread I have that now installed in Google Chrome,

polonus