Update highcharts-chart.component.ts

[fclmman]

Added _zone.runOutsideAngular for highcharts stuff, as it hardly affects application performance due to multiple eventListeners inside highcharts itself

[KacperMadej]

Hi @fclmman

Before we could accept the PR we'll need more info about the issue it's related to and what exactly is the "stuff" you mentioned.

[fclmman]

Hi, @KacperMadej, thank for such quick response. What i mentioned is an issue, that can be seen when the application is quite complex, and your page consists of multiple components. It can happen on some enterprise application, where you have huge datagrid and highcharts chart on one page, for example. What i meant by stuff is multiple asynchronous work and eventlisteners that exist inside the highcharts. And as we know it triggers andular's changedetection. So when you track a series in chart with your mouse, highcharts fires lots of point mouseenter events, each of them triggers changedetection, which is really slowing down a huge app. To prevent it we can run highcharts code outside of zone, and prevent multiple changedetections.

[KacperMadej]

@fclmman

Thank you for all the information.
Is the window.setTimeout really needed? Looks like a not a perfect solution.

[fclmman]

@KacperMadej well, you were right, no need in timeout here, updated the pull request

[KacperMadej]

I had more time run more tests. The idea is interesting and solution for the problem works. It's possible to still use _zone.run() in chart's events if anyone wants to trigger change detection, so we are not taking away any features. The new way of running the wrapper should be optional to prevent breaking backward compatibility. Because of this the code will look differently, but will be based on your suggestions @fclmman , so thank you very much for all the help.

We'll need to prepare some documentation for the new feature.
I'll shortly open an issue for better tracking.

[fclmman]

Well, if you dont mind i can provide optional runotside, so that current behaviour will stay as default

[KacperMadej]

@fclmman

If you could test new version 2.2.0 and check related commit (2ebcb07) to ensure that the suggested solution resolved the problem.