You were right, there was another issue. I naively did A Bad Thing by
to a secondary thread. Everything still worked ok unless I tried to
then it behaved unexpectedly as described earlier. When I changed my
Not really. There is a BeforeNavigate or BeforeNavigate2 event that gets
fired before the Navigate actually happens where you get a chance to stop
the navigation By calling Stop() on the lpDisp variabe that it passes to
the
method. But first you must stop using Navigate and start using Navigate2
instead. Navigate doesn't work in IE 6 and later.
I don't think that no connection would cause the webbrowser control to
crash. There is something else that is wrong, you have to find that, but
no
way to tell until you move to Navigate2(). Actually you need to use all
the
xxxx2() methods like Refresh2() if you are using Refresh().
AliR.
"jshouk@*removethis*gmail.com" <jsh...@gmail.com> wrote in message
news:1175020195.960865.88690@d57g2000hsg.googlegroups.com...
On Mar 27, 1:34 pm, "David Ching" <d...@remove-this.dcsoft.com> wrote:
Could you expand on what you mean by "internal navigation"? If you
don't
call Navigate(), the browser shouldn't navigate! :-)
Right, but if the web page I load in the control with Navigate() has
links of its own in it, or if it has a meta refresh tag in it, or
something similar, then the control will continue to show new pages
beyond the scope of my program. That's what I mean by "internal
navigation". Once I've loaded that first page, it's out of my hands!