Comments on: .NET Web Browser Control Gotchas

By: Karthik

Karthik — Mon, 11 Jan 2010 15:49:43 +0000

@Kenia – I m not sure if the control offers any ajax support. I know you can hook into DOM events in the browser and do things.

@Richard – WebBrowser1.Document.ExecCommand(”Print”, True, 0)? Can you try passing in a “false”? WebBrowser1.Document.ExecCommand(”Print”, false, 0). It worked for me so I dont see any reasons why it wont for you.

By: Richard

Richard — Fri, 08 Jan 2010 14:47:41 +0000

WebBrowser1 is displaying a PDF file.

I added a Print button to display the printdialog box. It tried to do the following but it doesn’t work.

Help pls. Thanks!

Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button2.Click
Try
WebBrowser1.WebBrowserShortcutsEnabled = True
WebBrowser1.Document.ExecCommand(“Print”, True, 0)

Catch ex As Exception
MsgBox(“oops..” & ex.Message)
End Try
End Sub

By: Kenia

Kenia — Tue, 11 Aug 2009 13:39:31 +0000

Anything regarding Ajax support? So far I haven’t found a way to get notified when a call is made using the XMLHttpRequest object. Do you guys know if there’s any specific tricky event that fires or is it that the WebBrowser control simply can’t access to this?

By: Mark

Mark — Fri, 10 Jul 2009 01:08:47 +0000

I have an application that won’t allow buttons on a website to fire the html click code for submit…something new in the i.e webbrowser control has broken how buttons work…do you have any idea???

By: Karthik

Karthik — Tue, 07 Jul 2009 14:35:23 +0000

@Bob I know there is a way to suppress script errors by doing this “WebBrowser.ScriptErrorsSuppressed = true”. I think this should work if the IE setting to display script errors is ignored.

By: Bob Breeding

Bob Breeding — Mon, 06 Jul 2009 05:19:33 +0000

The “gotcha” I’ve run into is that the webobject is great at throwing script errors and ignoring your IE settings to disable the display of script errors. Given that the webobject appears to be based on IE 6, most recent sites and just about all embedded ads throw these errors. You know of any way to suppress script error reporting?

thanks,
breeding@cox.net