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
The events.selection callback function should have correct x-axis min and max values reflecting the selected range.
Actual behaviour
In the events.selection callback function the x-axis max is incorrect with some range selections. For example, with following screenshot selection, the x-axis max is around 1, but it should be around 0.5.
Seems that the bug appears when the selection range min is left side of the zero point. I can also see, that the min value doesn't go lower than 0 even though the x-axis left border is less than 0 (not sure if that is desired).
Assuming that the same issue is with the x-axis min value when selecting a range near the right border.
Live demo with steps to reproduce
Issue can be replicated with this demo (make a mouse selection shown in the above screenshot): https://jsfiddle.net/50Lq6jfh/
Expected behaviour
The events.selection callback function should have correct x-axis min and max values reflecting the selected range.
Actual behaviour
In the events.selection callback function the x-axis max is incorrect with some range selections. For example, with following screenshot selection, the x-axis max is around 1, but it should be around 0.5.
Seems that the bug appears when the selection range min is left side of the zero point. I can also see, that the min value doesn't go lower than 0 even though the x-axis left border is less than 0 (not sure if that is desired).
Assuming that the same issue is with the x-axis min value when selecting a range near the right border.
Live demo with steps to reproduce
Issue can be replicated with this demo (make a mouse selection shown in the above screenshot): https://jsfiddle.net/50Lq6jfh/
Product version
Highcharts v11.4.1
Affected browser(s)
Likely all browsers
I believe this issue is related to #20784.
The text was updated successfully, but these errors were encountered: