tag:blogger.com,1999:blog-8266872010677720335.post614359668592540475..comments2023-06-29T12:48:22.121+02:00Comments on WatiN and more: Catching server errors with WatiNJeroenhttp://www.blogger.com/profile/05989461179391848268noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-8266872010677720335.post-41211747349271893862008-07-11T08:39:00.000+02:002008-07-11T08:39:00.000+02:00Hi Bryan,I think your solution is OK as well. In t...Hi Bryan,<BR/><BR/>I think your solution is OK as well. In the past I had some problems with using the events. It seemed to influence the stability of WatiN. That's the reason why I still shy away from using events from the DOM and shdocvw dlls in WatiN (and thus can't provide this functionality).Jeroenhttps://www.blogger.com/profile/05989461179391848268noreply@blogger.comtag:blogger.com,1999:blog-8266872010677720335.post-67034322291893032522008-07-10T19:27:00.000+02:002008-07-10T19:27:00.000+02:00Thanks for this. Though the main limitation is th...Thanks for this. Though the main limitation is that each solution will have to provide their own IE subclass that knows how to detect server errors, etc.<BR/><BR/>I wrote a code sample, based on your approach, except I tapped into the native InternetExplorer event model to trap native errors, such as 404, etc.<BR/><BR/>http://stupiddumbguy.blogspot.com/2008/07/catching-server-errors-with-watin-redux.html<BR/><BR/>Can you see any limitations to this ?bryanhttps://www.blogger.com/profile/01332614158223702009noreply@blogger.com