JavaScript Method results in Non Secure Item IE6

Question

So I am baffled by this one. I have a function that is responsible for a non-secure item warning message to appear when viewing my web page from with IE6 on SSL. If I comment out the entire function the message goes way. If I just comment out the one method call it remains. What is really driving me nuts is if I remove all of the logic from within the method.... the message remains???!!! I literally have to comment out the whole method including the signature. The method contains JQuery library logic but I don't see why that would matter when all of the function logic is commented except for the signature. Has anyone seen this before?

Here is the function:

function styleNavigationCorners() {
        if (!($.browser.msie && $.browser.version.substr(0, 1) == '6')) {
            $(".DecisionPointTitle").corner({
                tl: { radius: 8 },
                tr: { radius: 8 },
                bl: { radius: 8 },
                br: { radius: 8 },
                antiAlias: true,
                autoPad: false
            });
            $(".DecisionPointHeadline").corner({
                tl: { radius: 8 },
                tr: { radius: 8 },
                bl: false,
                br: false,
                antiAlias: true,
                autoPad: false
            });
            $("#NavigationFooter").corner({
                bl: { radius: 8 },
                br: { radius: 8 },
                tl: false,
                tr: false,
                antiAlias: true,
                autoPad: false
            });
        }

    }

This still gives me the non-secure warning? :

   function styleNavigationCorners() {
//            if (!($.browser.msie && $.browser.version.substr(0, 1) == '6')) {
//                $(".DecisionPointTitle").corner({
//                    tl: { radius: 8 },
//                    tr: { radius: 8 },
//                    bl: { radius: 8 },
//                    br: { radius: 8 },
//                    antiAlias: true,
//                    autoPad: false
//                });
//                $(".DecisionPointHeadline").corner({
//                    tl: { radius: 8 },
//                    tr: { radius: 8 },
//                    bl: false,
//                    br: false,
//                    antiAlias: true,
//                    autoPad: false
//                });
//                $("#NavigationFooter").corner({
//                    bl: { radius: 8 },
//                    br: { radius: 8 },
//                    tl: false,
//                    tr: false,
//                    antiAlias: true,
//                    autoPad: false
//                });
//            }

        }

I have searched for duplicate function signatures have found none. Can anyone help? Thanks!

-Nick

Answer 1

Is this inside a script tag? Or is the script included with the src attribute? If it is inside the script tag, I have no clue why it would be doing that.

Also, can you give us a link to this page?

---

Try:

<script type="text/javascript" src="https://path/to/file"&gt;&lt;/script&gt;

Answer 2

Can I assume you are using the curvy corners jquery wrap? If so then you will find the following issue with that library. It runs the following on ie6

  document.write("<script id='__ie_onload' defer='defer' src='javascript:void(0)'><\/script>");

Setting the src to void will cause the non secure warning. IIRC you could try changing this to javascript:false - again another hack or even include a blank file on the server and point to that to avoid the warning for sure. Whatever you opt for youll have to change the source library.

Just as an aside - Do you really need those corners? 26k minified of js is a hefty price to pay!

Answer 3

IE6 contains a bug here.

JavaScript-protocol URIs are treated as insecure, and this results in a mixed content warning when they are encountered. See my answer here: http://stackoverflow.com/questions/96382/how-to-tell-what-files-ie-thinks-are-nonsecure/1022020#1022020 for a tool that will help you verify that it's the JavaScript-protocol URI causing the issue.