I have feeling that this might be related to the way ChromeDriver handles clicks (in case you use Chrome). Practically, when you send "click" to ChromeDriver, it clicks not on the element, but on its coordinates. So, if element position has changed after getting coordinates, the misclick will happen.
If that is the case, you should add some explicit waitings in place. Otherwise, this might be a bug in WebDriver. --- Reply to this email directly or view it on GitHub: https://github.com/watir/watir-webdriver/issues/209#issuecomment-20979063
_______________________________________________ Wtr-development mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-development
