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
As you can see in my example screenshots if you have a long category its text ends up being cut off depending on screen width. If I understood the documentation correctly one could set the x.axis.height according the the longest category text in the chart, but my problem is a little different since these categories are generated dynamically, so I have less control over the length they have other than they're between 1-255 chars.
That said, I'm wondering if there's any other option that would:
increase the chart height dynamically depending on the longest category text
ellipsify the text according to the max height of the chart element
do something else that would make the chart look less broken? :)
While searching for similar issues I found this one that might be related to what I'm asking here as well.
The text was updated successfully, but these errors were encountered:
jcsmorais
changed the title
x.axis cuts off if window width size is small and category label exceeds chart height
x.axis cuts off if window width size is small and category text exceeds chart height
Apr 7, 2018
C3 version: 0.5.2
D3 version: 4.12.0
Browser: Chrome
OS: OSX
Code pen: https://codepen.io/jcsmorais/pen/pLQPwR
Screenshots:
As you can see in my example screenshots if you have a long category its text ends up being cut off depending on screen width. If I understood the documentation correctly one could set the x.axis.height according the the longest category text in the chart, but my problem is a little different since these categories are generated dynamically, so I have less control over the length they have other than they're between 1-255 chars.
That said, I'm wondering if there's any other option that would:
While searching for similar issues I found this one that might be related to what I'm asking here as well.
The text was updated successfully, but these errors were encountered: