Closed cuserox closed 3 months ago
Latest commit: 6c711d70a07434bd178ca315a9bc7f7856f8c6b8
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
Small non blocking UI difference, seems like there is a 4px
padding for the DownshiftInput
list container that's not being applied, and only the 4px
for the list items is being applied
4px
padding
4px
+ 4px
padding
Proposed change:
8px
horixontal padding:
Can we make the values right aligned and only truncate the name if needed? Right now it truncates even if enough space would be available
Can we make the values right aligned and only truncate the name if needed? Right now it truncates even if enough space would be available
@six7 something like this? Leaving the flex containers for the name & value to fight amongst themselves, depending on which one needs the space the most 😄
Why does this PR exist?
Closes #2878
The ability to view full token data (specifically names) was a pain point for users, which was solved by stacking these (PR). Negative feedback means we are reverting this, and aligning both views to horizontally display the data.
What does this pull request do?
mentions.css
&Mentions
to have the same look & feel asDownshiftInput
when displaying an item on the listTesting this change
{...
= MentionsSamples of updated UI