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

[BUG] y-axis labels are being cut off for apparently unknown reason #5106

Closed
ed1nh0 opened this issue Jan 3, 2018 · 7 comments
Closed

[BUG] y-axis labels are being cut off for apparently unknown reason #5106

ed1nh0 opened this issue Jan 3, 2018 · 7 comments

Comments

@ed1nh0
Copy link

ed1nh0 commented Jan 3, 2018

Looking for similar issues I found that issue #729 show big numbers being cut off in the y-axis. But in my case the problem occurs when I have decimal values lower than 1.
Please take a look at my screenshot.
The first graph shows y-axis labels being cut off while the others below show them as expected.
I drawed a dashed yellow line just to show the <canvas> limits.

chartjs issue

I tried set up padding and width for the <canvas> tag but with no success.

@ed1nh0
Copy link
Author

ed1nh0 commented Jan 3, 2018

I guess I found the answer.

Stackoverflow link.

@etimberg
Copy link
Member

etimberg commented Jan 3, 2018

@ed1nh0 do you have a fiddle that reproduces this?

@ed1nh0
Copy link
Author

ed1nh0 commented Jan 4, 2018

@etimberg I'm really sorry. I've tried but I can't reproduce this issue.
All I know is the answer I found on Stackoverflow fixed this.

@ed1nh0 ed1nh0 changed the title y-axis labels are being cut off for apparently unknown reason [BUG] y-axis labels are being cut off for apparently unknown reason Jan 4, 2018
@Drecula
Copy link

Drecula commented Jan 4, 2018

Your so link is -404

@jcopperfield
Copy link
Contributor

@ed1nh0 and @etimberg I think this is the same as Issue #4441 and should be fixed with PR #4942

@ed1nh0
Copy link
Author

ed1nh0 commented Jan 5, 2018

@Drecula sorry about that. I fixed the link.

@jcopperfield it seems to be the same indeed but I couldn't reproduce it as described.

@simonbrunel
Copy link
Member

Closing this issue because as @jcopperfield wrote, it might have been fixed by #4942 (released in 2.7.2) but we can't verify since no test case has been provided.

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

No branches or pull requests

5 participants