Here's my problem, I'm working on a site that has a list of items within a window on the page. The list of items is longer than the window they are displayed in, so it has a scroll bar to navigate the list. It's an odd list in that it's defined by divs and ul tags only.
Initially I used actions to scroll the list and select items. Everything seemed fine. Then I ran tests in all the major browsers only to discover Safari doesn't support actions--back to the drawing board. (It struck me as odd that this long after actions were introduced the SA driver didn't support them, but such is life.)
I updated the code to use JS code to do the scrolling instead. Here's the code:
((JavascriptExecutor) driver).executeScript("arguments[0].scrollIntoView(true);", element);
I did a bunch of local testing in FF, CH and SA and everything worked fine. Then I set up a Jenkins job to run a few tests in all the browsers, and the everything looked good until it got to CH. Mind you, running the same tests locally using CH works perfectly. Heck, even IE worked fine and that never happens.
When I run the tests in CH on our grid, every test gets the same basic error trying to click something that has been scrolled into view:
unknown error: Element is not clickable at point (395, 269). Other element would receive the click: <div class="plans_tabs_contents">...</div>
(Session info: chrome=40.0.2214.115)
(Driver info: chromedriver=2.12.301326 (093c7e07b4a916b690e784b0374c7f618f1ea4be),platform=Mac OS X 10.8.1 x86_64)
Looking at screen shots at the failure point shows the items are in view, and not obscured, at least visually.
I've using the same options for the local SA driver and the Remote Driver. I can't think of what else could be different than the local execution and the grid execution. I'm looking for any suggestions of other things to check at this point.
Really, what I want is all the drivers to work the same way.
Thanks in advance.