You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Safari (No ghosting in chrome, but the tracker element still lingers):
1: zoom to a range smaller then boostThreshold.
2: zoom to a smaller range that contains only couple hundred points ... notice the ghosting in safari
3: inspect the src svg element <g class="highcharts-series highcharts-series-0 highcharts-tracker" ...> that is created.
note: there are 4 path elements and 1 image element.
4: click on the zoom reset button in the Highchart graph.
5: inspect the svg element <g class="highcharts-series highcharts-series-0 highcharts-tracker" ...>
note: there are now 2 path elements and 1 image element.
Bug: I believe that the second path element - - should be destroyed in the method boost.src.js:destroyGraphics() This artifact (depending on the size of the tracker element) can destroy performance and memory in Safari.
node: depending on the threshold the tracker element can be very large.
Cheers,
Clay
The text was updated successfully, but these errors were encountered:
I noticed that the boost module leaves a "highchart-tracker" svg path when the graph is reset. It's completely reproducible on the demo site.
http://www.highcharts.com/component/content/article/2-news/175-highcharts-performance-boost
In Safari (No ghosting in chrome, but the tracker element still lingers):
1: zoom to a range smaller then boostThreshold.
2: zoom to a smaller range that contains only couple hundred points ... notice the ghosting in safari
3: inspect the src svg element <g class="highcharts-series highcharts-series-0 highcharts-tracker" ...> that is created.
note: there are 4 path elements and 1 image element.
4: click on the zoom reset button in the Highchart graph.
5: inspect the svg element <g class="highcharts-series highcharts-series-0 highcharts-tracker" ...>
note: there are now 2 path elements and 1 image element.
Bug: I believe that the second path element - - should be destroyed in the method boost.src.js:destroyGraphics() This artifact (depending on the size of the tracker element) can destroy performance and memory in Safari.
node: depending on the threshold the tracker element can be very large.
Cheers,
Clay
The text was updated successfully, but these errors were encountered: