-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Launcher does not work with Firefox 61 #88
Comments
Have you found a solution @steve-todorov? Having the same issue :( |
Unfortunately no - this also started happening with the newest Chrome version as well. Seems like they've changed something under the hood which is breaking Our solution was to create a docker image with fixed Firefox version |
Chromium v68 is working fine for us. We've pinned Firefox for now, too. |
Update using the Firefox on my macOS works fine, while the alpine version is broken for us (https://pkgs.alpinelinux.org/package/edge/testing/x86_64/firefox) |
I was able to fix the issue in our Dockerfile with Alpine. It seems the |
Thanks for posting an update! We were having so much issues with the alpine image and the different browsers, that we gave up on using it for running node/npm related tests with karma/protractor. We now use |
I am having a similar issue with Firefox 62. Karma starts, but as soon as it triggers Firefox in headless, it just hangs. I can see Firefox in the OSX Dock, but it doesn't open, and no active application indicator is displayed either. Here is my karma.conf.js file;
|
Is there some documentation about running a docker-image of Firefox (like alpine-based or https://hub.docker.com/r/jlesage/firefox) while using the native host (node/npm & toolchain)? |
It seems like something has changed in Firefox 61 which has resulted in
karma-firefox-launcher
to be unable to properly start firefox. The following configuration works fine for firefox 60.The text was updated successfully, but these errors were encountered: