Skip to content
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.

fix(firefox): Fix directConnect for Firefox 51+ #3953

Merged
merged 6 commits into from
Jan 18, 2017

Conversation

heathkit
Copy link
Contributor

Fixes #3823.

@heathkit heathkit force-pushed the firefox-51-direct branch 2 times, most recently from 25c3580 to 33e573c Compare January 11, 2017 21:24
@heathkit
Copy link
Contributor Author

Putting this on hold for now. We can manually install the beta on circle and test with direct connect, but the other tests against Firefox need selenium server. It's too much work to have some tests in Circle on Firefox 51 and some on Firefox 47, so I'm going to wait a bit for Firefox 51 to be released and hopefully a new selenium server release.

@heathkit
Copy link
Contributor Author

So this works now. Users that want to use Firefox 51+ will need to use selenium server 3.0.0-beta4, using the same method that the circle.yml does.

webdriver-manager update
wget http://selenium-release.storage.googleapis.com/3.0-beta4/selenium-server-standalone-3.0.0-beta4.jar -P ./node_modules/webdriver-manager/selenium
webdriver-manager start --versions.standalone 3.0.0-beta4

@@ -14,11 +14,17 @@ dependencies:
post:
- ./node_modules/.bin/gulp lint
- ./node_modules/.bin/webdriver-manager update
- ./node_modules/.bin/webdriver-manager start:
background: true
- wget http://selenium-release.storage.googleapis.com/3.0-beta4/selenium-server-standalone-3.0.0-beta4.jar -P ./node_modules/webdriver-manager/selenium
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note to self: Can't use 3.0.0 or 3.0.1, as these both have a bug that breaks firefox.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants