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

Weird horizontal lines show up after zoom-in on a boosted column chart #7716

alirezameftahi71 opened this Issue Jan 23, 2018 · 5 comments


None yet
3 participants

alirezameftahi71 commented Jan 23, 2018


We have a column chart with totally 40000 data in 4 series. But sometimes when we zoom in, we see a some random horizontal lines which are not supposed to be there.
See we zoom in the highlighted area of the chart like shown below:
screenshot 294

Expected behaviour

What we expect is to zoom-in and not see any random horizontal lines on the chart.

Actual behaviour

But this is what we get:
screenshot 295

Live demo

Check the jsfiddle link below:

Product version

Highcharts 6.0.4

Affected browser(s)

Tested on:
Firefox, Chrome


This comment has been minimized.


KacperMadej commented Jan 23, 2018

Hi @alirezameftahi71

Thank you for reporting about the problem.

After second zoom the lines are not visible - at least for me after testing this.

Internal note: not fixed in any (1, 2) currently opened boost bugfix branches


This comment has been minimized.


cvasseng commented Jan 30, 2018

A fix has been pushed for this, and is pending merging.

Preview of the fix:


This comment has been minimized.


cvasseng commented Feb 2, 2018

Fixed in 6.0.5.

@cvasseng cvasseng closed this Feb 2, 2018


This comment has been minimized.

alirezameftahi71 commented Feb 3, 2018

Thank you @cvasseng . But there seems to be a problem.
When I use the gitHub link in the jsFiddle, the issue IS fixed. But when I use the CDN, the lines still exist.
I opened the CDN link and at the top it says it's the version 6.0.5.
Fixed with github version of boost.js :
NOT Fixed in 6.0.5 release of boost.js:


This comment has been minimized.


cvasseng commented Feb 5, 2018

We had an issue with preparing the release, resulting in this particular fix not making it into 6.0.5.

There will be a maintenance release very soon that addresses this as well as a couple of regressions.

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