Library does not function properly on IE11

I’m submitting a … (check one with “x”)

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here

Current behavior IE11 Throwing an animation error.

Here is the stack trace: at _contains (http://192.168.1.92:4200/vendor.bundle.js:111033:41) at NoopAnimationDriver.prototype.containsElement (http://192.168.1.92:4200/vendor.bundle.js:111078:77) at TransitionAnimationEngine.prototype._balanceNamespaceList (http://192.168.1.92:4200/vendor.bundle.js:114345:17) at TransitionAnimationEngine.prototype.createNamespace (http://192.168.1.92:4200/vendor.bundle.js:114318:13) at TransitionAnimationEngine.prototype.register (http://192.168.1.92:4200/vendor.bundle.js:114369:13) at AnimationEngine.prototype.register (http://192.168.1.92:4200/vendor.bundle.js:115419:9) at AnimationRendererFactory.prototype.createRenderer (http://192.168.1.92:4200/vendor.bundle.js:181176:9) at DebugRendererFactory2.prototype.createRenderer (http://192.168.1.92:4200/vendor.bundle.js:161361:9) at createComponentView (http://192.168.1.92:4200/vendor.bundle.js:159965:9) at callWithDebugContext (http://192.168.1.92:4200/vendor.b"

Expected behavior IE11 to work

Reproduction of the problem https://swimlane.github.io/ngx-charts/

The error is present on the demo page. You can see the errors in console on IE11.

"TypeError: Object doesn’t support property or method ‘contains’

What is the motivation / use case for changing the behavior? Allowing IE11 to work

• ngx-charts version: 5.3.1, 5.2.1

• Angular version: 4.2.4

• Browser: [IE 11.0 ]

• Language: [all | TypeScript X.X | ES6/7 | ES5]

[Belaroth]

It looks like Angular changed something with Animations that broke ngx-charts. I was able to get it working again by adding the polyfills: import ‘core-js/es7/array’; import ‘classlist.js’;

and the shim: if (typeof SVGElement.prototype.contains == ‘undefined’) { SVGElement.prototype.contains = HTMLDivElement.prototype.contains; }

It’s not a fix but at least it gets it working in 6.0.0

[alexandermikuta]

The latest version (6.0.0) still seems to have this error.