nightwatch: nightwatch does not work with selenium node-firefox-debug:3.5+
This issue was referenced before in https://github.com/nightwatchjs/nightwatch/issues/1600 and was closed as the original author was able to go back to 3.4. Not being able to use nightwatch with a current firefox build is still an issue though.
I tried @yak80 solution in that issue and found it to work as expected. Would like this issue reopened as we are still stuck using 3.4 which is quite dated.
a quick recap of the issue. If you try to use various methods like click with the 3.6 selenium docker version you will get an error message like this:
localizedMessage: 'Element reference not seen before: undefined\nBuild info: version: \'3.6.0\', revision: \'6fbf3ec767\', time: \'2017-09-27T16:15:40.131Z\'\nSystem info: host: \'055e4e3d90a0\', ip: \'172.21.0.4\', os.name: \'Linux\', os.arch: \'amd64\', os.version: \'4.9.49-moby\', java.version: \'1.8.0_131\'\nDriver info: driver.version: unknown',
systemInformation: 'System info: host: \'055e4e3d90a0\', ip: \'x.x.x.x\', os.name: \'Linux\', os.arch: \'amd64\', os.version: \'4.9.49-moby\', java.version: \'1.8.0_131\'',
supportUrl: null,
cause: null,
suppressed: [],
message: 'Element reference not seen before: undefined\nBuild info: version: \'3.6.0\', revision: \'6fbf3ec767\', time: \'2017-09-27T16:15:40.131Z\'\nSystem info: host: \'055e4e3d90a0\', ip: \'x.x.x.x\', os.name: \'Linux\', os.arch: \'amd64\', os.version: \'4.9.49-moby\', java.version: \'1.8.0_131\'\nDriver info: driver.version: unknown',
hCode: 1093878616,
class: 'org.openqa.selenium.JavascriptException',
buildInformation: null }```
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 7
- Comments: 31 (2 by maintainers)
Commits related to this issue
- fix #1683 #1628 — committed to chris-tn/nightwatch by chris-tn 6 years ago
- Move e2e tests from PhantomJS to headless Chrome Candidate resolution of issue #33, "Resolve Travis CI Nightwatch failures since #32 resolution". Moving away from PhantomJS as its development has be... — committed to markafitzgerald1/cribbage-analyst by markafitzgerald1 6 years ago
For what it is worth “SE_OPTS=-enablePassThrough false” on testing for me today does not appear to be working for me with:
The result is:
Also 3.9 was just released and that drops passthrough entirely so doesn’t work there so a new approach is needed to handle the webdriver session with firefox.
The question is more about, why on Earth is this PR #1604 still open? Shouldn’t it have been merged by now? It does meet the specs: https://w3c.github.io/webdriver/webdriver-spec.html#x11-elements
Where it says:
@straris - think this is a nightwatch issue and how firefox works with it. You can make firefox work with latest standalone-firefox but not the node variants. I also read that enablePassThrough was a depreciated feature which will be removed shortly… If not already in subsequent docker releases for selenium