On Wednesday 18 September 2002 6:26 pm, you wrote: > You guys rock! > It was the javascript in the body tag alright. It was referencing a > function that at some point was probably in the page, but now lives in web > limbo. I'm curious how you all managed to spot it so quickly. I have > been banging my head over it for a couple of days on and off now (which is > okay because I went ahead and made the page essentially compliant).
One of the most helpful things to use when you're looking for Javascript errors is Netscape. The one thing that Netscape is very good at is Javascript debugging. It'll give you a true error message indicating the line the error is actually on, and often even highlights the dodgy section and points at the error with an arrow as well as telling you what's wrong. To get Netscape's Javascript console up to see the errors, type "javascript:" without the quotes into the address bar. IE's JS error messages are normally wrong - it never gives any real detail and often even lies about which line is causing the error!! HTH Dave P ____ � The WDVL Discussion List from WDVL.COM � ____ To Join wdvltalk, Send An Email To: mailto:[EMAIL PROTECTED] Send Your Posts To: [EMAIL PROTECTED] To change subscription settings to the wdvltalk digest version: http://wdvl.internet.com/WDVL/Forum/#sub ________________ http://www.wdvl.com _______________________ You are currently subscribed to wdvltalk as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED]
