Closed luke-hill closed 3 years ago
Update: Based on https://github.com/site-prism/site_prism/pull/93/commits/6468fc70c76b53df1dce30a4f6dcbe6ea92469d1 this proves that using the latest webdrivers won't work with old versions of selenium
@luke-hill Thanks for reporting this issue. I was able to use your repo and Gemfile.low_spec
to reproduce the error in v4.6, but not in v4.5, which tells me that the bug was introduced by this change. I think adding this check back will fix it:
if ::Selenium::WebDriver::Service.respond_to? :driver_path=
::Selenium::WebDriver::Edge::Service.driver_path = proc { ::Webdrivers::Edgedriver.update }
end
@titusfortner Any reason to not use the above?
Selenium 3 only supports the legacy Edge HTML, which was force removed from Windows machines last month. Selenium 4 only supports the new Chromium Edge. The Edge support in webdrivers has always been Chromium-only and previously required running off of github / trunk in order to work.
So no, there is no Edge support from webdrivers in Selenium 3, only in latest Selenium 4 beta. We can make that more explicit in the README if necessary.
Just catching back up to this. So the actionable bit here is advise users not to use webdrivers v4.5+ with selenium < 3.11
Summary
Started getting failures in CI using latest webdrivers and an "old" gemfile.
Debug Info
https://github.com/site-prism/site_prism/runs/2123477812
Expected Behavior
Webdrivers to run
Actual Behavior
Note, I don't test on Edge. So this is likely a minor bug.