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
We found this bug after upgrading Highcharts from v10 to v11. In v10 this is working correctly, so this is a regression in v11.
After the v11 upgrade the yAxis has the correct range without the boost module, but when the boost module is added the yAxis range is incorrect.
Expected behaviour
For scatterplots with multiple series and many data points the max value of the yAxis should be calculated based on the series with the largest range, as in the image below (where the boost module is not enabled):
Actual behaviour
The yAxis max is calculated based on the series with the most data-points, but with a smallest range, as in the image below (with boost module enabled):
Live demo with steps to reproduce
Open this jsFiddle to see the chart with the boost module enabled, and observer the yAxis only goes up to 1400: https://jsfiddle.net/vdjsep39/2/
We've realised that as a workaround we could use a single scatterplot series and style each individual data point. But this approach has some downsides in terms of memory usage and pre-processing of the data. Furthermore, since this is a breaking change not mentioned in the changelog, we still consider this to be a bug and prefer to await a resolution before upgrading to v11.
Background
Expected behaviour
For scatterplots with multiple series and many data points the max value of the yAxis should be calculated based on the series with the largest range, as in the image below (where the boost module is not enabled):
Actual behaviour
The yAxis max is calculated based on the series with the most data-points, but with a smallest range, as in the image below (with boost module enabled):
Live demo with steps to reproduce
Product version
Highcharts Core 11.4.8
With Highcharts boost module (also on 11.4.8)
Affected browser(s)
All
The text was updated successfully, but these errors were encountered: