Read more

Selenium may break with ChromeDriver 75+

Jakob Scholz
June 06, 2019Software engineer at makandra GmbH

This fix is not recommended anymore since Chrome 91 will raise further issues. It looks like recent Selenium versions don't have any issues with the w3c interface anymore.

When you update your ChromeDriver to version 75 or beyond, you might get w3c errors in your tests.

Illustration UI/UX Design

UI/UX Design by makandra brand

We make sure that your target audience has the best possible experience with your digital product. You get:

  • Design tailored to your audience
  • Proven processes customized to your needs
  • An expert team of experienced designers
Read more Show archive.org snapshot

For example, reading the browser console for errors no longer works, and page.driver.browser.manage.logs.get(:browser) will raise an error like "undefined method `log' for #<Selenium::WebDriver::Remote::W3C::Bridge:0x000055903f307aa8>".

Add options.add_option('w3c', false) to your Selenium configuration (e.g. features/support/selenium.rb) and you should be back to normal:

Capybara.register_driver :selenium do |app|
  options = Selenium::WebDriver::Chrome::Options.new(args: %w[--disable-infobars])
  options.add_option('w3c', false)
  Capybara::Selenium::Driver.new(app, browser: :chrome, options: options)
end
Posted by Jakob Scholz to makandra dev (2019-06-06 14:47)