John Brock
2009-09-14 19:26:50 UTC
I am using Visual Basic 2008 Express to write a Windows Forms
application that displays HTML/JavaScript pages in a WebBrowser
control. (I'm setting the form as the WebBrowser's ObjectForScripting
and calling "window.external.whatever()" from JavaScript when I
want JavaScript to call functions in the app).
Right now it can be very difficult to find bugs in the JavaScript
code. If I set ScriptErrorsSuppressed = False I sometimes get a
helpful popup. Or I can scatter JavaScript alert popups through
the code. But it would be very nice to have a real debugger! So
I'm trying to find out if there are any standard (or even non-standard)
ways to debug JavaScript in this situation.
(Note that I have IE8 installed on my PC. I understand there is
a spiffy new JavaScript debugger that comes with IE8 -- it's part
of the Developer Tools that pop up if I hit F12 while in IE. It
would be very nice to be able to use this to set breakpoints in
pages displayed in the WebBrowser, but there is no obvious way to
do this, as F12 does nothing here).
application that displays HTML/JavaScript pages in a WebBrowser
control. (I'm setting the form as the WebBrowser's ObjectForScripting
and calling "window.external.whatever()" from JavaScript when I
want JavaScript to call functions in the app).
Right now it can be very difficult to find bugs in the JavaScript
code. If I set ScriptErrorsSuppressed = False I sometimes get a
helpful popup. Or I can scatter JavaScript alert popups through
the code. But it would be very nice to have a real debugger! So
I'm trying to find out if there are any standard (or even non-standard)
ways to debug JavaScript in this situation.
(Note that I have IE8 installed on my PC. I understand there is
a spiffy new JavaScript debugger that comes with IE8 -- it's part
of the Developer Tools that pop up if I hit F12 while in IE. It
would be very nice to be able to use this to set breakpoints in
pages displayed in the WebBrowser, but there is no obvious way to
do this, as F12 does nothing here).
--
John Brock
***@panix.com
John Brock
***@panix.com