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 a table that uses <JSONFormat> to render cell contents, it's easy to produce columns that look like this:
To an user, it can be confusing why some cells use normal ellipses + a browser tooltip and others have a fancy popover that renders longer content. In the source code, it is clear that this truncation threshold is 80 characters, and you get into this undesirable state when columns are < 80 chars wide while content length hovers above and below 80 chars.
No clean solution jumps out to me. Changing the truncation threshold might help, but feels a bit like a band-aid. Some ideas:
Change the "..." icon that triggers the popover
Never use text-overflow truncation & browser tooltips with <JSONFormat> -- instead always use the fancy popover
Thoughts?
The text was updated successfully, but these errors were encountered:
Just talked to Bill, we propose using the fancy popover truncation not just for JSON cells anymore, but for any type of cells. That will make the interaction consistent across all cells that are truncated.
A request for micro-interaction design review
In a table that uses
<JSONFormat>
to render cell contents, it's easy to produce columns that look like this:To an user, it can be confusing why some cells use normal ellipses + a browser tooltip and others have a fancy popover that renders longer content. In the source code, it is clear that this truncation threshold is 80 characters, and you get into this undesirable state when columns are < 80 chars wide while content length hovers above and below 80 chars.
No clean solution jumps out to me. Changing the truncation threshold might help, but feels a bit like a band-aid. Some ideas:
text-overflow
truncation & browser tooltips with<JSONFormat>
-- instead always use the fancy popoverThoughts?
The text was updated successfully, but these errors were encountered: