Repository navigation
fillField failing for good "field" #345
Description
Activity
I'm facing similar issue which may be related to this one – the
$page->getContent()returns valid HTML code, but$page->find('css', 'html')returnsnull. The same occurs for every other valid tag and id.yes;
$page->getContent()does return the DOMI 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
I seem to get this error on Firefox 68 with GeckoDriver as well.
Still digging in to see if I can figure out the culprit.
I think this is documented as in issue in the GeckoDriver repository: mozilla/geckodriver#1581
It's odd that it seems to affect both Chrome and Firefox equally
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)
Reacted by vargedoAnd 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
behat.ymlfile, I get this (note theextra_capabilities,chromeOptions,w3c:false)default: suites: default: contexts: - nwcontext:form - nwcontext:formstone - nwcontext:select2 - FeatureContext extensions: Novaway\CommonContexts\Extension: ~ Behat\MinkExtension: base_url: http://localhost/crm selenium2: browser: chrome capabilities: browserName: "chrome" extra_capabilities: chromeOptions: w3c: falseReacted by vargedo and heliortfReacted by heliortfReacted by heliortf- added a commit that references this issue
on Jul 12, 2019 also related: instaclick/php-webdriver#84
- added a commit that references this issue
on Jan 3, 2020 - added a commit that references this issue
on Aug 22, 2020 - added a commit that references this issue
on Sep 6, 2020 - added a commit that references this issue
on Nov 7, 2020 - added a commit that references this issue
on Nov 23, 2020 - added a commit that references this issue
on Jan 19, 2021 - added a commit that references this issue
on Nov 24, 2021
Seeing a weird issue when running ChromeDriver 75, Behat 3.5.0, MinkExtension 2.3.1 on Windows with Selenium
Every call to
MinkContext::fillFieldfails becauseBehat\Mink\Element::findAllreturns null, and I get anElementNotFoundException.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?