I'm running into an issue on a client site where the client primarily uses IE9. On the secure site, the client hard coded an http rather than https. In setting the IE security settings to "prompt" for mixed content, any currently running script appears to be stopped once the browser hits the non secure script and the console log reports all these scripts as causing the security problem. If I set the IE security settings for mixed content to "disable", IE only reports in console the non secure calls and correctly runs the secure scripts IE reported as 'bad' under the prompt setting.
Has anyone else experienced this and is this an issue that's documented somewhere?
Thanks.