selenium: Firefox driver in 2.53.4 not working with Firefox 48

Meta -

OS: OSX

Selenium Version: 2.53.4

Browser: Firefox

Browser Version: 48

Expected Behavior -

Firefox starts and is able to be controlled via Selenium

Actual Behavior -

Firefox starts, but does nothing. After waiting long enough, I see an error like: “`connect_until_stable’: unable to obtain stable firefox connection in 60 seconds”.

Steps to reproduce -

Selenium::WebDriver.for :firefox

Downgrading to Firefox 47.0.1 resolves this issue for me.

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Reactions: 3
  • Comments: 30 (5 by maintainers)

Commits related to this issue

Most upvoted comments

Can’t fix.

In Firefox 48, Mozilla requires extensions to be signed. They have refused to sign Selenium’s Firefox driver extension (webdriver.xpi). Feel free to contact them and/or log an issue for them at https://bugzilla.mozilla.org

The way forward now is to use GeckoDriver. Which is now the default implementation used in 3.0-beta

This issue has been known as a long time coming, I highly recommend pinning your automation to use Firefox 45 ESR until a release of using GeckoDriver/marionette is stable enough for your tests.

We tried to give Firefox+GeckoDriver another chance since a lot of stuff landed in Firefox recently and now we run our Protractor tests with Firefox 55 in headless mode. No extension. Pretty sweet!

I would advice anybody following this ticket who still runs an old Firefox version with WebDriver or stopped running tests against Firefox at all to try again. Especially since headless mode landed!

You can either set the MOZ_HEADLESS=1 or run with the --headless parameter. I think v55 only works on GNU/Linux in headless mode but so does our Jenkins 😃

Note that there are some version dependencies when using the same Firefox installation also with the new Gecko driver. The classic driver should work with any version that doesn’t check for a Mozilla signature, but a newer version of Firefox will require newer version of the Gecko driver as well. This is especially true with the Firefox Developer versions. Newer versions of the Gecko driver also require a newer Selenium version.

I’ve created a repository for RHEL/CentOS 7 builds of Firefox 52 ESR without the Mozilla signature checking: https://copr.fedorainfracloud.org/coprs/jschwart/firefox-allext/

This build has been verified to work with: Selenium RC (2.53) Classic driver (3.0, 3.4) Gecko driver, 0.14.0 (which will work with at least Selenium 3.0) and also with 0.16.1 (which will work with Selenium 3.4)

I expect that this build is compatible with pretty much any Selenium driver/version combination.

I managed to run Protractor tests with the latest Firefox and my own webdriver. more info here

download the latest gecko driver and unzip it and Set System Properties for Gecko Driver

Yeah. Follow the steps in that URL- you should be able to

http://toolsqa.com/selenium-webdriver/how-to-use-geckodriver/

@liapretorius Capybara will support selenium with geckodriver when they’re feature complete enough to pass Capybaras tests. You can see the current status of those tests using the latest versions of selenium, geckodriver and firefox here - https://travis-ci.org/jnicklas/capybara/jobs/163764567 . All of the failures are caused by currently lacking functionality in the combo of latest selenium, geckodriver, and marionette (No actions API, modal prompt issues, send_keys functionality limitations)