Open jason1122g opened 2 years ago
Thanks @jason1122g , this is a good callout. I wonder if making individual vizualization creators responsible for the tooltip width/layout is the right way to go, though, or if we could do a better job with the default automatic layout. I'll keep this in mind as part of the work on a unified charting approach and library.
Added to the UX backlog for further research and brainstorming.
@joshuarrrr could we take both paths? We first improve the default/automatic layout approach and also allow the visualization builder to modify for handling any aesthetic needs for the specific viz case. These would make it so individual visualization creators are not responsible for the tooltip width/layout by default but still allows them to control their output to handle aesthetics or edge cases.
@ahopp I think that's a good idea in theory, but I'd only hesitate because of backwards compatibility concerns - each direct UI control we add is reflected in the chart configuration object which we'll have an obligation to respect.
Personally, I would hesitate to make aesthetics customizable for different viz cases, because to me, that opens the floor to more and more things being customizable. In theory, I think that would be nice, however with more and more things changing from one viz to another can make it difficult for multiple people to work on a viz because they aren't used to its specific aesthetic settings.
Maybe in this specific case it would be fine because its something that's so minor, but I think parity is something that should be kept in mind when thinking about aesthetic differences between viz cases.
Is your feature request related to a problem? Please describe.
We have many visualizations showing long text as tooltip. But the default tooltip width is too short which makes us feel difficult to read.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
Sometimes it is difficult to read a sentence in multiple lines