Thank you for the reply, this will be a great workaround and actually provides some needed functionality.
I updated my Watir/Selenium/Chrome/Chromedriver and the problem persists. Is this a known issue for certain situations, or do I need to dig deeper into my code? On Wednesday, February 1, 2017 at 5:00:26 PM UTC-5, Titus Fortner wrote: > > Out of curiosity, what isn't compatible with updating selenium? > > For scrolling elements, check out p0deje's 'watir-scroll' gem. It's great > when what selenium does by default isn't quite good enough. > > Titus > > > On Wednesday, February 1, 2017 at 8:36:06 AM UTC-6, Brian Rieck wrote: >> >> Watir-webdriver: 0.6.11 >> Selenium-webdriver: 2.35.1 >> Chromdriver: 2.27.440174 >> Chrome: 56.0.2924.76 >> >> I am forced to use an older watir-webdriver version as there are other >> dependencies that conflict with updating selenium. I have run into an >> issue with elements that are out of view. The tests believe they have >> interacted with the element and even bring it into view. However, the >> resulting action does not in fact click a button that was out of view, only >> bring it into view. Does anyone know a workaround for this other than >> "update your stuff". >> >> >> Thank you. >> > -- -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. [email protected] http://groups.google.com/group/watir-general [email protected] --- You received this message because you are subscribed to the Google Groups "Watir General" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
