[thelist] Norton Firewall blocking Javascript

Jeff Howden jeff at jeffhowden.com
Tue Sep 2 14:13:29 CDT 2003


keith,

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> From: Quedgeley Church Site
>
> onclick="{ openNewWindow('http://www.cofe.anglican.org');
>          return false; }"
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

minor quibble completely unrelated to your question, but those curly braces
are completely unnecessary.

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> but stops after the <BODY> presumably when it sees a
> packet containing the onclick attribute invoking the
> function.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

probably because he has popup blocking enabled.

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> So can anyone confirm that this is out of the box
> behaviour not someone being over-zealous and what do
> you guys suggest as a way round it?
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

tell him he's an idiot.  ok, be nicer about it than that.  the link *works*
without scripting.  so, why's he complaining?  either shut up or turn off
whatever it is on his system that's keeping it from working.

an alternative might be some scripting that would run either at the bottom
of the page or onload that would loop over the links collection, adding the
onclick event handler to each and every external link.  a bonus from that is
not having to do that manually anymore.

since proxies/firewalls like zonealarm and norton do string filtering, it's
highly unlikely they'll be able to stop that sort of approach since the
assignment of the onclick event handler happens on the client, rather than
via the html.

good luck,

.jeff

------------------------------------------------------
Jeff Howden - Web Application Specialist
Résumé - http://jeffhowden.com/about/resume/
Code Library - http://evolt.jeffhowden.com/jeff/code/




More information about the thelist mailing list