Find elements will auto scroll them into my headerbar.

[chrismatheson]

Hi,

Im having a problem with my tests just now and im not sure how to go abotu fixing it. This may be awebdriver problem rather than a protractor one, im no sure.

My site has a fixed nav bar at the top, and on some elements when i use findElement() it will scroll them to the "top" of the page, which is underneath my header bar so when i try to click() them i get the following error

UnknownError: unknown error: Element is not clickable at point (728, 7). Other element would receive the click:

...

i was wondering if there is a way to specify the "padding" space my site requires or do i need to manually scroll after every findElement() ??

Any help or pointers to other reading material would be fantastic.

P.S when i finally solve this i intend to raise a PR adding to FAQ's for the next poor fellow :)

[juliemr]

Hi,

Yup, this is the default webdriver behavior. However, there may be a way around it: webdriver provides a capability to change the behavior of scrolling: https://code.google.com/p/selenium/wiki/DesiredCapabilities#Read-write_capabilities (see elementScrollBehavior), which lets you change it so that elements scroll to the bottom of the viewport. This claims to only be supported in IE and firefox. Hopefully it'll be coming to other drivers soon!

https://code.google.com/p/chromedriver/issues/detail?id=647

[lukas-shawford]

Running into this exact same scenario, where the element I'm trying to click on is underneath a fixed navbar. In my case, I just scrolled to the top manually:

ptor.executeScript('window.scrollTo(0,0);').then(function () {
    page.saveButton.click();
})

[e-oz]

This answer helped me: http://stackoverflow.com/a/21942415/680786

[msafi]

As a current workaround, I get Protractor to execute this script when it loads the page to unfix the nav bar just for the tests:

browser.executeScript("document.querySelector('.header').style.position = 'absolute'")

[juliemr]

Closing this - I'm cleaning up old issues, and the external bug here has been closed as working as intended.