Skip to content
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

overflow:justify not working when using linkedTo (and even workaround is now broken) #3975

Closed
drmrbrewer opened this issue Mar 12, 2015 · 4 comments

Comments

@drmrbrewer
Copy link

commented Mar 12, 2015

The right-most label on the top x axis is cut off in the following (at least when the chart area is sized deliberately small enough), despite overflow:justify being used:

http://jsfiddle.net/drmrbrewer/qvztq2qy/7/

I understand that this issue was reported back in 2002 (#1328) so it's a bit frustrating that the issue is still there.

Nevermind, what is more frustrating for now is that a workaround for this issue has now also broken in the latest highcharts.

The workaround was to unlink the axes and to ensure to use the same settings for both axes. This is a working solution in highcharts 4.0.4:

http://jsfiddle.net/drmrbrewer/qvztq2qy/10/

But even that is now broken in highcharts 4.1.4:

http://jsfiddle.net/drmrbrewer/qvztq2qy/11/

Hopefully the root cause can be addressed so that a workaround is no longer required? Second best would be to make the workaround work again :-)

@drmrbrewer

This comment has been minimized.

Copy link
Author

commented Apr 25, 2015

Is there any plan to look at this?

Thanks.

@TorsteinHonsi

This comment has been minimized.

Copy link
Collaborator

commented Apr 27, 2015

overflow:justify was deprecated since 4.1.x and replaced by an automatic ellipsis when text overflows. So the question now is why the ellipsis doesn't show. I'll work on that right away.

@drmrbrewer

This comment has been minimized.

Copy link
Author

commented Apr 27, 2015

Great, thanks.

@drmrbrewer

This comment has been minimized.

Copy link
Author

commented Apr 30, 2015

Great, look forward to a new release soon with this fix applied. BTW, I think your copyright/licence notices in the code need updating to use 2015 as the latest year!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.