The basic one you get with XP has too many security holes. That one was IE6, and I'm running on Win7 so I use IE8. So yeah, I guess my IE would not work for some reason. However, I've discovered geckofx, and I'll look into that instead.
People if you want to use firefox/gecko instead of default WebBrowser just go to http://code.google.com/p/geckofx/. All the methods and properties are nearly the same (however the DocumentText property is missing). Also, if you need to set the inner text of anything don't set the provided property use SetAttribute("value",string). On Jun 21, 2:39 pm, Drew <[email protected]> wrote: > What version of IE are you running, usually I've had trouble with the > newer IE versions instead of the basic one you get with Windows XP. > > On Jun 21, 10:47 am, Anonymous <[email protected]> wrote: > > > No. Since I'm running WebBrowser, which in turn runs on IE, > > theoretically it should work the same, but in actual IE it works fine. > > > On Jun 21, 4:10 am, Cerebrus <[email protected]> wrote: > > > > Does this problem occur when you load the page in a browser (IE, for > > > instance) ? > > > > Ideally, the JS code in the page should run only after the page has > > > loaded (it should be invoked only before the ending </body> tag or > > > within <body onload="">. > > > > On Jun 19, 11:09 pm, Anonymous <[email protected]> wrote: > > > > > Right now, for debugging purposes, I've set a webbrowser control on my > > > > application to be visible. The webbrowser sometimes (occasionally) > > > > fires a documentcompleted event but the page hasn't finished loading > > > > yet (the control is blank white still). In the javascript on the > > > > page, one line of code uses the getElementById method, but for some > > > > reason, even though the "document is completed" the element somehow > > > > hasn't loaded yet and the javascript returns an error because it > > > > couldn't find an element with that id. > > > > I don't get why documentcompleted doesn't fire properly.
