Issue metadata
Sign in to add a comment
|
Selenium Chromedriver will not scroll element into view before click
Reported by
matthew....@sixt4.io,
Sep 6 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.79 Safari/537.36 Steps to reproduce the problem: 1. Have a webpage with a link that is outside of current viewport 2. Issue a click command via selenium 3. Element is not clicked What is the expected behavior? The element is clicked (page navigates) What went wrong? The element is not clicked Did this work before? Yes 60 Chrome version: 61.0.3163.79 Channel: stable OS Version: 10.0 Flash Version: If I scroll the element into view before issuing the click command, selenium will click the element successfully
,
Sep 6 2017
,
Sep 6 2017
matthew.lymer@, what version of chromedriver are you using? Similar issue (https://bugs.chromium.org/p/chromedriver/issues/detail?id=1852) was fixed in Chromedriver v2.32. If you are not using this version, please make sure to update. You can download the binary from https://sites.google.com/a/chromium.org/chromedriver/downloads
,
Sep 7 2017
I'm currently using ChromeDriver 2.31.488763 (092de99f48a300323ecf8c2a4e2e7cab51de5ba8), I'll test with v2.32 and let you know.
,
Sep 7 2017
Thank you for providing more feedback. Adding requester "gmanikpure@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 7 2017
I still receive the issue, but now it's intermittent: System.InvalidOperationException: unknown error: Element is not clickable at point (769, 1100) (Session info: chrome=61.0.3163.79) (Driver info: chromedriver=2.32.498550 (9dec58e66c31bcc53a9ce3c7226f0c1c5810906a),platform=Windows NT 10.0.15063 x86_64) at OpenQA.Selenium.Remote.RemoteWebDriver.UnpackAndThrowOnError(Response errorResponse) at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters) at OpenQA.Selenium.Remote.RemoteWebDriver.InternalExecute(String driverCommandToExecute, Dictionary`2 parameters) at OpenQA.Selenium.Remote.RemoteWebElement.Execute(String commandToExecute, Dictionary`2 parameters) at OpenQA.Selenium.Remote.RemoteWebElement.Click() If I manually scroll to the given element, it is clicked properly.
,
Sep 7 2017
For a workaround, I am doing (via Selenium):
((IJavaScriptExecutor) _driver).ExecuteScript("arguments[0].scrollIntoView(true);", _element);
_element.Click();
,
Sep 7 2017
Thanks for trying the test with Chromedriver v2.32. Looks like some scenario might have been missed during the fix of chromedriver: issue#1852 . Could you please share your reproducible test along with the page under testing?
,
Sep 8 2017
Sure, it'll take a while to make a small reproducible example. I'm using dotnet core for my tests, if I host it on github would that work, or is there a preferred language?
,
Sep 8 2017
Yes, that would be fine. Also, please provide chromedriver verbose log. Thanks.
,
Sep 11 2017
,
Sep 11 2017
,
Sep 19 2017
Unable to triage this issue from TE end, hence adding TE-NeedsTriageHelp label for further triage
,
Sep 19 2017
Awaiting the response from matthew.lymer@.
,
Sep 20 2017
I haven't forgot, the workaround is working for me at the moment, but coming up with an example is still on my list of things to do.
,
Sep 20 2017
Thank you for providing more feedback. Adding requester "gmanikpure@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 4 2018
Closing this issue as it had no activities for a long time. Will re-open if we receive additional information to allow us to investigate further. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by matthew....@sixt4.io
, Sep 6 2017