Well, the easiest method would be to discover the JS error content manually, and disable the options in your browser for stopping on errors, and/or displaying the contents of JS errors during browsing. Automation isn't always the best solution.
Otherwise, Jarmo has a great function for discovering and taking screenshots of JS errors on his blog/github: http://itreallymatters.tumblr.com/ On Jul 29, 9:48 am, carmen3lia <eliaol...@gmail.com> wrote: > The application has a few JS errors and when I run the script, it is > stopped because the erors, How I can catch the errors and the script > can follow executing. I'm using Internet Explorer 7 and 8 -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. You received this message because you are subscribed to http://groups.google.com/group/watir-general To post: watir-general@googlegroups.com To unsubscribe: watir-general+unsubscr...@googlegroups.com
