-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
tests failing on IE/Edge #1373
Comments
I am on Mac, will figure some way to test on IE browsers. |
The official IE VMs are quite good: https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/ |
The issue might actually be simpler. Both these test cases use a custom matcher Thanks for the links to the VMs - will use those. |
That's great. Yes, you'll find that a lot of the matchers do funny things for M$. Thanks for all your hard work! |
fixed by #1378 |
Microsoft uses subtly different syntax for a lot of style values, also within the CSS/HTML spec but a different interpretation.
It looks like we have two tests failing on all IE/Edge because of this:
https://saucelabs.com/beta/tests/d992de1575c24c07b289df4b65ddf55f/jsunit
@kum-deepak, do you have access to these browsers? We used to be compatible back to IE9 (!!) and if d3.js still is, we should still be too. But I think testing on IE11 and latest Edge is sufficient.
It's strange that we only do saucelabs cross-platform tests when pushing to a branch, not for PRs. It takes quite a bit longer (3min vs 1min), perhaps that was the reasoning. What do you think about changing that?
If you want to see these failures, go to the Travis build history
https://travis-ci.org/dc-js/dc.js/builds
and click a failing build, go to the end of the log and it will give you links to the failing builds at saucelabs.
The text was updated successfully, but these errors were encountered: