This is not a bug, but incorrect usage of Watir. There is something happening
in your application under test which you don't properly handle (e.g.
`StaleElementReferenceError` indicates that DOM is updated and your old element
should be relocated, `UnhandledAlertError` indicates that JavaScript popup is
on the page).
Also, few notes:
1. Stacktrace shows that `Selenium::WebDriver::Error::UnhandledAlertError` is
raised, not `StaleElementReferenceError`.
2. The loop of course works fine without these 2 lines because you don't
operate with element and thus, it's not being located.
3. If you think that this is a real bug (while it's not), always provide
relevant HTML and Ruby code so we could reproduce.
---
Reply to this email directly or view it on GitHub:
https://github.com/watir/watir-webdriver/issues/237#issuecomment-31993816
_______________________________________________
Wtr-development mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-development
