Don’t know if you resolved this problem, but I have just resolved the same issue from the other side. It appears Selenium and Firefox have difficulty talking to each other – I suspect Firefox ‘evolve’ changes over a number of releases, so backward and forward compatibility are not always guaranteed, and incompatibility always seems to … Read more
I solved these kinds of problems using the webdrive manager. You can automatically use the correct chromedriver by using the webdrive-manager. Install the webdrive-manager: Then use the driver in python as follows This answer is taken from https://stackoverflow.com/a/52878725/10741023
Use findElements instead of findElement. findElements will return an empty list if no matching elements are found instead of an exception. To check that an element is present, you could try this This will return true if at least one element is found and false if it does not exist. The official documentation recommends this method: findElement should not be … Read more
ok, the answer is in error message – “Other element would receive the click: …” I had the same problem when I just started using selenium, couldn’t figure out what’s the problem. “Other element would receive the click: …” means there is other element above(overlapping) your element(pop up window, page is grayed out(disabled while loading, … Read more
Updating Firefox and Selenium solved it for me. I don’t pretend to have an explanation for the root cause however. Updated Firefox 48 → 53 Updated to Selenium 3.4.1 I also reinstalled/updated Geckodriver using Homebrew and explicitly used it as an executable for Selenium WebDriver, but it turned out that it wasn’t necessary to mitigate … Read more
The Selenium client bindings will try to locate the geckodriver executable from the system PATH. You will need to add the directory containing the executable to the system path. On Unix systems you can do the following to append it to your system’s search path, if you’re using a bash-compatible shell: export PATH=$PATH:/path/to/geckodriver On Windows … Read more
You may try to switch to the window again after the redirect. Save you window handle: redirect to the page you want and then call switchTo using the window handle: Does your page contain any frames? It may also be possible that you are not in the correct frame after the redirect.
I’m trying to scrape a page, but I sometimes have trouble clicking a link/button. When the web page loads, then the “loadingWhiteBox” will appear first and then disappear after a few seconds (but it will remain in the HTML code) as long as the box is appears on the website, I can not click on … Read more
You can use document.evaluate: Evaluates an XPath expression string and returns a result of the specified type if possible. It is w3-standardized and whole documented: https://developer.mozilla.org/en-US/docs/Web/API/Document.evaluate Expand snippet There’s also a great introduction on mozilla developer network: https://developer.mozilla.org/en-US/docs/Introduction_to_using_XPath_in_JavaScript#document.evaluate Alternative version, using XPathEvaluator: Show code snippet
You have two buttons with given xpath on this page, first is not visible, thats why you are getting ElementNotVisibleException One is under <div class=”loginPopup”> Second (the one you need) is under <div class=”page”> So change your xpath to look like this, and it will fix your problem: