-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
karma 1.4.0 broke IE8 support #2556
Comments
Here's greenkeeper's issue against the videojs project which alerted me to this: videojs/video.js#3946 |
Thank you for the report. If you could help us figure out what exactly the issues are, that would be great. As far as I understood socket.io broke IE8 but fixed it later at which point I upgraded the dependency. But it sounds like sth ist still not right. |
I'll make a PR for the es3 preset and I'll investigate the socket.io thing. Thanks for the quick response! |
The es3 preset PR: #2557 |
So, the socket.io issue is that uglify 2.7 disabled support for IE8 in a minor version update. Since karma uses the minified file it broke. Switching to the unminified file works great. I'll open an issue/PR against socket.io-client |
I opened up an issue against socket.io-client: socketio/socket.io-client#1063 An easy workaround is to serve the socket.io-client file manually and only use the unminified file as that one works. I'll check back in next week. |
Karma 1.4.0 indavertantely broke IE8 when updating socket.io. This pins karma to 1.3.0 a version that is known to work on IE8. See karma-runner/karma#2556 See socketio/socket.io-client#1063
Karma 1.4.0 indavertantely broke IE8 when updating socket.io. This pins karma to 1.3.0 a version that is known to work on IE8. See karma-runner/karma#2556 See socketio/socket.io-client#1063
Karma can't be updated to 1.4 as it breaks on IE 8 & lower: karma-runner/karma#2556 Grunt can't be updated to 1.x as the old grunt-jscs peer-depends on Grunt 0.4 and in npm 2 (used by default in Node 4 LTS) this breaks npm install. Updating grunt-jscs to a newer version (or switching to ESLint) would require lots of style fixes.
Does anyone know of a workaround for this? I can't seem to get IE8 working even if I downgrade Karma to 1.3.0. |
@exogen Sizzle uses Karma 1.1.1 and it seems to work with IE 8 and even 7: https://travis-ci.org/jquery/sizzle. |
@mgol Thanks for the tip! After I couldn't get 1.1.1 to work either, I started looking at other dependencies. It works after swapping out |
@exogen look at karma-runner/karma-jasmine#105 and karma-runner/karma-mocha#104 maybe this is your case |
Karma can't be updated to 1.4 as it breaks on IE 8 & lower: karma-runner/karma#2556 Grunt can't be updated to 1.x as the old grunt-jscs peer-depends on Grunt 0.4 and in npm 2 (used by default in Node 4 LTS) this breaks npm install. Updating grunt-jscs to a newer version (or switching to ESLint) would require lots of style fixes.
Karma can't be updated to 1.4 as it breaks on IE 8 & lower: karma-runner/karma#2556 Grunt can't be updated to 1.x as the old grunt-jscs peer-depends on Grunt 0.4 and in npm 2 (used by default in Node 4 LTS) this breaks npm install. Updating grunt-jscs to a newer version (or switching to ESLint) would require lots of style fixes.
Karma can't be updated to 1.4 as it breaks on IE 8 & lower: karma-runner/karma#2556 Grunt can't be updated to 1.x as the old grunt-jscs peer-depends on Grunt 0.4 and in npm 2 (used by default in Node 4 LTS) this breaks npm install. Updating grunt-jscs to a newer version (or switching to ESLint) would require lots of style fixes. Closes gh-399
As outlined in the linked issue, it looks like our loose version range allowed a newer Karma to be install that breaks in old IEs. Karma issue tracker link: karma-runner/karma#2556 For now, pinning to 1.3.0 resolves a transitive dependency tree which "works".
As outlined in the linked issue, it looks like our loose version# range allowed a newer Karma to be install that breaks in old IEs.# On branch debug-ci Karma issue tracker link:# modified: karma-common.js karma-runner/karma#2556 modified: package.json For now, pinning to 1.3.0 resolves a transitive dependency tree which "works".
As outlined in the linked issue, it looks like our loose version range allowed a newer Karma to be install that breaks in old IEs. Karma issue tracker link: karma-runner/karma#2556 For now, pinning to 1.3.0 resolves a transitive dependency tree which "works".
Can anyone in this thread verify that this issue is fixed on master with socket.io version 2.0.3? |
I had a test run in Video.js using the latest karma from github and it seems to be working (commit): https://travis-ci.org/videojs/video.js/builds/313129759 |
@dignifiedquire any change we could get a new release of karma? The update to socket.io seems to have fixed this issue. Thanks! |
2.0.0 is out and seems to be working great! Closing this issue as addressed. Thanks! |
Great to hear, and sorry for it taking so long.
…On 21. Dec 2017, 19:11 +0100, Gary Katsevman ***@***.***>, wrote:
2.0.0 is out and seems to be working great! Closing this issue as addressed. Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
It happens, thanks for your hard work! |
Expected behaviour
Running karma in IE8 is possible.
Actual behaviour
IE8 does not work anymore.
Environment Details
karma --version
):karma.config.js
fileKarma version: 1.4.1
My karma config is available here
Steps to reproduce the behaviour
0.0.0.0:9876
once it loadsI noticed this first when greenkeeper updated the dependency to karma 1.4.0. After several travis build retries, it still wouldn't connect to IE8 (see build).
It looks like it's related to the socket.io update and probably broke inadvertently.
Dropping back down to version 1.3.0 of karma, everything works great still.
Potential solutions, they're not mutually exclusive:
es3
preset to make sure that words likedefault
are quoted properly.I'd be happy to try and help making the first two options happen. In the meantime, I'm staying with the 1.3.0 version of karma.
The text was updated successfully, but these errors were encountered: