Firefox 50 and latest protractor/selenium. Timeout issues.

[inthegarage]

I've decided to see what was happening with Firefox 50, latest selenium and protractor
Here are my versions.

• Node Version: v5.10.1
• Protractor Version: 4.0.11
• Angular Version: 1.4.9
• Browser(s): Firefox 50
• Operating System and Version Windows 10
• Selenium 3.0.1
• Firefox driver: 0.11.1 (gecko driver)
  When I use the same test framework on Chrome or Internet explorer, everything just runs fine in my test
  However when I use Firefox 50, I get many timeout related errors:

Failed: Error while waiting for Protractor to sync with the page: "[ng:test] http://errors.angularjs.org/1.4.7/ng/test"
Or
Failed: Error while waiting for Protractor to sync with the page: "window.angular is undefined

The place where you get these errors seems to be random.

The tests are the same for all browsers, my capabilities are as follows from the test file:

    capabilities: {
        'browserName': 'firefox',
        marionette : true,
    }

What is the current status of Firefox and Protractor? Is it supported? Do I need any other options or different versions?

[juliemr]

FireFox support is definitely in flux at the moment. Please see http://www.protractortest.org/#/browser-support - we still recommend firefox 47.

Behind the scenes - we're also still trying to figure out how to support geckodriver with firefox for versions higher than 48.

[inthegarage]

Hi Julie,

Thanks for the reply. Firefox 50 with the above framework seems much more stable then 49 say and other variants. This seems very close now and my tests nearly worked.
It would appear that there just needs to be some tweaking to do, possibly in the Protractor side, but I'm no expert as to where the problem may actually lie.
Shall I keep this ticket open so we can track progress, or is that mechanism really reflected in the link you provided?

[sjelin]

(assigning to you @mgiambalvo because I didn't assign many over issues to you, and I feel like I need to balance)

[commutecat]

To mitigate Firefox multi-process architecture incompatibilities with any web testing tools , use Firefox ESR 45.
https://www.mozilla.org/en-US/firefox/45.3.0/releasenotes/

[inthegarage]

Although that certainly tests any software on Firefox, it doesn't test it on 50+, that is what most users will be using and more importantly what most customers will require.
I will raise this issue with Selenium as suggested, although currently the issue(s) seems to be in both products.

[heathkit]

Firefox 50 has a bug that affects timeouts in webdriver injected scripts. This bug has been fixed, and we should support testing in Firefox 51+