The sink is not enough...

• • Reply

  15 years ago

  by gee666

  Gee

  , United Kingdom

  Joined 15 years ago

  This is in reference to a previous post: http://www.developerfusion.co.uk/forums/thread/122991/

  I thought I had solved it, but the NavigateError event does not fire for javascript errors.  Does anyone have any other ideas on how to trap javascript errors programmatically for the webbrowser object??

  Thanks

  Gee

   

  Report abuse
• • Reply

  15 years ago

  by gee666

  Gee

  , United Kingdom

  Joined 15 years ago

  The following property is *supposed* to catch script errors at runtime:

  webBrowser.Document.Window.Error += new handler blurb

  But it doesn't :(

  It can only be attached AFTER the document has loaded and the DocumentCompleted event fires *after* IE has issued all of it's javascript error dialogs :(

  Subclassing the browser hasn't helped and if I use the SuppressScriptErrors property, then I will have no chance of catching them!

  Any ideas???

   

  Report abuse
• • Reply

  14 years ago

  by jverco

  John Verco

  , United States

  Joined 14 years ago

  I just had a similar problem with a VB.NET application that I am working on which uses the WebBrowser control.

  Set the property:

  WebBrowser.ScriptErrorsSuppressed = True

  in the method that handles the event WebBrowser.DocumentCompleted.

  After doing this I have not encountered any javascript error popups.

  Report abuse