Hi Jon,
We have one client that actually uses Norton Internet Security suite. IMHO that suite should be banned from existence... anyway.. the problem is that apparently, the popupblocker that comes with it automagically inserts some symantec jscript to interfere with javascript on the page. This is what is inserted :
<script language="JavaScript">
<!--
function SymError()
{
return true;
}
window.onerror = SymError;
//-->
</script>
See here for "info" on this on the symantec website: http://service1.symantec.com/SUPPORT/nip.nsf/16c1d01d537bf4d188256d8e0076b346/f497e345525fa9e488256dbf007118ac?OpenDocument&src=bar_sch_nam
In searching for a solution to deal with this, i found this interesting thread over at webmasterworld.com: http://www.webmasterworld.com/forum91/1696.htm (registration required).
The funny thing is that this error only surfaces on a page that is called "advertenties" (dutch for advertisements), and this quote from that thread seems to point in that direction:
I found out one thing the hard way!
Symantec Norton antivirus has a very stupid implementation.
It blocks all links used in Javascript, that have either the word "ad" or "ads" as part of the URL!
And because of this lots of legitimate URLs which are not malicious are getting blocked, giving the functionality of some sites a good beating...
I am very surprised by the way Symantec is hiding this issue... They are just telling "Just put the ad blocker off" ..
Hope this info helps you all.
also, one suggestion that looks promising is this:
I have not looked at this issue since I originally posted. But there is little point in inserting <!-- and -->. Javascript doesn't ignore these commands, HTML does! They are, of course, designed for old non-JS browsers to ignore javascript commands.
What you have to insert is /* and */. These commands comment out entire blocks of JS. So, you place the following at the top of your file:
/*
<script language="javascript">
</script>
*/
And then you will find that Norton will change it and you will end up with:
/*
function SymError()
{
return true;
}
<script language="javascript">
</script>
*/
I hope this makes sense. I have quite a complex JS script and the above works perfectly, so unless we are dealing with a new version of Norton (etc...) I see no reason why it should not work for you.
The reason i am posting here is that this might have serious impact on how DNN pages are viewed by our customers. Errors like this are something none of us are waiting for to happen, but they happen none the less. If this was Utopia, i'd hope for Shaun to put a minute of his time towards calling the nice folks of Symantec and inform them about the errors of their ways. Realising that that will never happen, might it be too much too ask for a solution in the client api?
Cheers,
Erik