New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Axis.breaks doesn't display all points #4229

pawelfus opened this Issue May 26, 2015 · 5 comments


None yet
4 participants

pawelfus commented May 26, 2015



  • use scrollbar and move it to the right

In the console observe errors:

Invalid value for attribute d="M -Infinity 281 L -Infinity 291
Invalid value for attribute x="-Infinity"


gapSize is not necessary, but it's easier to observe the issue.

@pawelfus pawelfus added the Highstock label May 26, 2015

@TorsteinHonsi TorsteinHonsi assigned ghost and unassigned ghost May 27, 2015


This comment has been minimized.


sebastianbochan commented Jun 11, 2015

  • 1

This comment has been minimized.


TorsteinHonsi commented Jun 15, 2015

Apparently the navigator doesn't translate correctly to the main X axis. The offset accumulates as we scroll towards the right, and culminates at the far right where we run out of corresponding X values.

The problem seems to lie in the breakSize option. When it is 0, the translation is correct:


This comment has been minimized.


TorsteinHonsi commented Jun 15, 2015

The commit above fixes the problems in the right end of the navigator.

The remaining problem now is when scrolling the navigator across the empty area (the weekend). It gives a straight line, and sometimes even full sections of the main series. See Click "Set extremes 2".


This comment has been minimized.

grzesiekgs commented Jun 16, 2015

I've tested your example and found something which might be related to this issue.

click "set extremes 3" at least twice. Observe extremes in console. Navigator seems to stay in one place, but extremes change every time the button is clicked.
You can also recreate it by clicking "set extremes 3" once, and moving navigator just a little bit.

Edit : updated example with code from master branch.


This comment has been minimized.


TorsteinHonsi commented Jun 16, 2015

Thanks, but I think that's a problem with the test rather than with Highstock itself. The test is based on mouse movements, but not all information is added to the simulated handlers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment