Hi,

>>
Care to describe this a bit better? Are you only talking about something like a call to alert()?
>>
Literally just insert the javascript line

debugger;

in the javascript code at the point you want the debugger to kick in - but I think you've worked that out now anyway.

>>
(Ok so I now realize I can navigate the VS instance of IE to my local file). It loads ok, but when I refresh it popups up a error messagebox do you want to debug, if I click yes it barfs on a complaint that my JIT degugging component registration is incorrect. So I ran the program it said to.. but now when I refresh the page I get a dialog about opening the debugger with a listbox of 3 choices:

New Instance of the MS Script Editor
New Instance of the MS Script Editor
New Instance of VS .Net 2003

so what the heck is wrong with the currently running VS instance???? And why it shows two instances of the script editor is rather odd too.
>>

Don't know why you're getting those choices - I get a single 'MS Script Editor' and, if VS .NET is loaded, an option like 'Output:Visual Studio .NET 2003' (the 'Output' bit varies depending on the active window in VS at the time) in addition to the .NET 'New Instance' option. But at least you can debug the script now ? :-)

I see you've made progress on the contains[] issue as well....
Regards,
Viv