Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
fillField failing for good "field" #345
Seeing a weird issue when running ChromeDriver 75, Behat 3.5.0, MinkExtension 2.3.1 on Windows with Selenium
Every call to
The referenced field is valid, and works in my CI tests (running older versions of dependencies and via SauceLabs)
I took a look at the generated xPath, and it looked really over-complicated(but might still have been valid).
I don't see anything in the selenium console logs to indicate a failed "find", but I'm not sure it would show there anyway.
Any pointers where to dig deeper?
I reverted my Chrome browser from Version 75 to Version 74, and also reverted my version of ChromeDriver.exe, and the problem appears to have gone away.
It would appear that something in the upgrade from Chrome 74 to Chrome 75 (or ChromeDriver) causes this issue
Ah ha. I think I uncovered some more details here.
It looks like, starting with Chrome 75, the selenium mode defaults to w3c, and the MinkSelenium2Driver is considering switching from instaclick/php-webdriver to facebook/php-webdriver, but is holding off because of PHP7 support: minkphp/MinkSelenium2Driver#293 (comment)
And a solution! (Or at least a temporary workaround):
In the thread above, they suggested turning off W3C mode for chrome.
So, adding that to my