Selenium 3 Firefox.click () not working

Question

Since I upgraded to the latest version of Selenium, my Firefox driver does not work correctly. Having not received a response from a Google / Stack search, I hope someone has an answer.

I created the object model of the page to enter the web page by clicking on the admin site and filling in the login / password + submit. This code was written for Selenium 2.53.6, but still works for IE and Chrome. The part that is not suitable for me is a line of code:

driver.find_element_by_xpath(locators["login.open"]).click() 

Locator:

 locators["login.open"] = "//*[@href='//www.phptravels.net/admin']" 

Since it works in IE and Chrome, then it puzzles me that Firefox can't .click() anymore?

I do not receive an error message in my console, it just does not press the admin button. Could this be related to this version of Firefox for Selenium 3 / geckodriver?

All drivers updated with pip

I use this site to practice my Selena: http://phptravels.com/demo/

Edit (1): I tried with Firefox versions 48 and 49 - still not working

Edit (2): geckodriver is configured using Firefox binaries, but the driver still does not execute .click()

 from selenium import webdriver from selenium.webdriver.firefox.firefox_binary import FirefoxBinary binary = FirefoxBinary('path/to/binary') driver = webdriver.Firefox(firefox_binary=binary) 

Edit (3): I check if the element is present by the xpath locator using is_displayed () and returns True . Therefore, I know that he can find the element.

Edit (4): 1) Tried with nightly build, as suggested, but not working. 2) Tried with find_element_by_link_text, also does not work. 3) I tried different versions of geckodriver (10.0, 11.0, 11.1 for 32 and 64 bits in all versions)

Edit (5): “The container for plugins for Firefox stops working” is generated sequentially every time a test case fails.

Edit (6): Possible solution to the problem . I did another test on another website, and Firefox successfully executes .click (). On the first target web page, where .click () crashes is a huge javascript that runs when the page opens. This could ruin the ability of geckodriver to do .click () on pages with heavy javascript.

Edit (7): Using .send_keys (Keys.RETURN) using the key library works , but additional reconfiguration may be required if you use POM. Explicitly performing some time. Hibernating will get you, but for now, it's still fragile to use Selenium 3 + Firefox / geckodriver to automate your web browser. Go to the latest stable version (2.53.6) if you need to test Firefox (note: the latest versions of Firefox do not work).

Answer 1

I have the same problem, but sometimes .click works, and sometimes not. This does not apply to switching to recently opened windows for me and several other quirks that cause tests that passed in Selenium 2.53.4, and which pass with Selenium 3 in Chrome, Safari and IE to crash in FireFox. I know this is not very specific, but I have already posted specific questions elsewhere.

I am using Ruby / Selenium / Capaybara. After extensive testing with the Selenium 3 / Geckodriver / FF49 combination, I returned to Selenium 2.53.4 / FF47.01. My impression was that the Selenium 3 / Geckodriver compiler is still not quite stable, which may or may not include Capybara compatibility with Geckodriver. I would like to be wrong. I browsed the Internet for any useful information and did not find it.

However, I found this note from the Selenium 3 blog announcement: “Mozilla was the leader in implementing the W3C WebDriver protocol. On the other hand, it revealed specification issues as it evolved, but it also means that Firefox support is hard to track because "Their engineering efforts were promising rather than supporting the current wired protocol used by Selenium WebDriver. At the moment, the best advice we can offer is to try the latest version of Hekkodriver and Selena together."

Answer 2

I used GeckoDriver v0.11.1 and selenium v3.0 and had the same problem. My workaround was to pass By.XPath instead of By.LinkText to FindElement. As mentioned in the OP, I was getting “true” when returning when searching for an item, it just didn't handle clicking on it for some reason.

  driver.FindElement(By.XPath("//something")).Click(); 

Answer 3

I am having the same problems right now, I was trying to use the nightly assembly, and it started working, although I am having problems with it, trying to click objects before they are ready, but that will be more of my problem than Selenium itself.

The current version for the night version is 52.0a1, which you can find here .

By default, FirefoxDriver will still use your normal Firefox installation, so you will need to create a Driver using the / options / binary profile, I do it this way (in C #, but should be very similar to Python);

var binary = new FirefoxBinary(@"C:\Program Files (x86)\Nightly\firefox.exe"); Driver = new FirefoxDriver(binary, null);

I think it could be FirefoxDriver(binary: binary) in Python, but not quite sure. Please note that using FirefoxBinary is obselete like Selenium 3 in favor of FirefoxOptions, but it will allow you to test if this is a problem at the moment.

Answer 4

I also encounter the same problem with 3 FF selenium, but is able to work with JS executor and Keys.RETURN or Keys.ENTER

With JS Artist:

 WebElement button = driver.findElement(By.cssSelector("input[value=btn]")); ((JavascriptExecutor) driver).executeScript("arguments[0].click();", button); 

With Keys.RETURN or Keys.ENTER :

 driver.findElement(By.id("abc")).sendKeys(Keys.RETURN); driver.findElement(By.id("abc")).sendKeys(Keys.ENTER); 

Answer 5

Could this be a mistake ?

In a week I will turn off the puppet (java):

capability.setCapability("marionette", false);

He restores everything . Do not ask me why.