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
In 8.15 a new handling of font-sizes has been introduced, moving it from being width-related to height-related. This was motivated by a series of considerations that are still valid but it could result in weird appearances for panels that are taller than large, or with very large numbers (lot of digits).
Example of problematic Metrics
In order to solve this, I would propose to introduce a way to take in consideration also the width of panel when defining the font-size of values so that value don't get cut off.
I would see two approaches to implement this solution:
Font-sizes are still determined according to break-points that take in consideration height of the panel, if the numbers are cut off their font-size automatically jumps to a smaller breakpoints, until it fit.
Same but instead of jumping to a smaller breakpoint, we automatically swtich to FIT function and get back to DEFAULT function as soon as the panel gets back to be big enough
Both options have pros and cons in terms of final look & feel but both will solve the original issue.
@gvnmagni, @markov00 - The integrations upgraded to 8.15.0 needs to get upgraded to the latest version to get this issue resolved without any changes to the metric visualisation?
In
8.15
a new handling of font-sizes has been introduced, moving it from beingwidth-related
toheight-related
. This was motivated by a series of considerations that are still valid but it could result in weird appearances for panels that are taller than large, or with very large numbers (lot of digits).Example of problematic Metrics
In order to solve this, I would propose to introduce a way to take in consideration also the width of panel when defining the font-size of values so that value don't get cut off.
I would see two approaches to implement this solution:
Font-sizes are still determined according to break-points that take in consideration height of the panel, if the numbers are cut off their font-size automatically jumps to a smaller breakpoints, until it fit.
Same but instead of jumping to a smaller breakpoint, we automatically swtich to
FIT
function and get back toDEFAULT
function as soon as the panel gets back to be big enoughBoth options have pros and cons in terms of final look & feel but both will solve the original issue.
Thanks to @MichaelMarcialis and @markov00 and @nickofthyme for the conversation around this topic.
The text was updated successfully, but these errors were encountered: