Before today, when someone connected to Passpack, Internet Explorer 6 would throw up an alert about there being non-secure items in the page. We’ve been trying to track down the cause for months now. Today, studying the history plugin I noticed that it prepends an iframe without source to the page body. That was the problem, and we’ve now fixed it.

Thank you very very much.
Sincerely,
Francesco

Yes, we’re using the older version of the history plugin. Since it seemed to be working well with all browsers, we let it as is. What’s strange is that Chrome is my preferred browser, and my Chrome doesn’t produce the history error so it wasn’t showing up in testing. Thanks for the heads up.

I studied the problem, and here’s what I found. You correctly noticed that there is an inconcistency between the two reported lines. This is an error, though the second shoud be:

var m = $.browser.netscape ? 1 : $.browser.msie ? 4 : 8;

I simplified it now, removing the Netscape condition since Netscape now is Mozilla-based. This, however, didn’t resolve the history problem which actually depends on the previous line:

var hh = parseInt(h);

Changing it as follows seems to fix the error:

var hh = parseInt(h,10);

When you don’t specify the numeric base in the parseInt call, Javascript should consider 10 as the default. But in some browsers, where the number string is ambiguous, I noticed the string value is considered as an octal string instead of a decimal string. The result of the parseInt command produced surprising values.

Can you let me know if this has fixed the error for you?
Thanks again.