List View truncates multi-select custom field chips needlessly

[lpb]

Please use the available width to fit as many chips as possible rather than always showing only one chip followed by “+n” and a tooltip:

See also / consider voting also for this:

Android Compact List View truncates custom field chips needlessly

Important note: To help us resolve your issue as quickly as possible, please ensure to fill out all the sections below. Do not share any private information such as email addresses or phone numbers - This is a public Forum! Briefly describe (1-2 sentences) the bug you’re experiencing: When in compact view on android, the custom field chips are truncated even though there’s plenty of horizontal room. This example shows with large font where it’s really bad, however it also happens with normal …

Thanks,

Larry

[lpb]

Yikes! About a half hour later I went to the same browser window that I hadn’t touched since the above screenshot and lo and behold it looks like this now:

I’m not sure what’s going on! Actually, this is how I thought it worked in the first place; I wasn’t expecting to add this request, but rather confirm an answer I intended to give in another post. Wondering if anyone has experienced anything like this?

[Bastien_Siebman]

I believe the engineering team has a hook so any new post by Larry goes straight to their inbox and they fast track the dev

[lpb]

@Bastien_Siebman

any new post by Larry goes straight to their inbox and they fast track the dev

I promise only to use my superpowers for good!

[Sarah_L]

Edit: Was getting mixed up with tags and custom field chips

Sorry, only just seeing this now. I still have the issue in my custom fields.

1. In tags for me, it displays them all (no [+1]) but with no indicator there are more, so the reverse happens where you have to increase the width of the field to check if there are or aren’t other tags. E.g. If you shrink your Social Media column it may only show Twitter and Instagram and not indicate there are two others.

2. In both custom fields (pictured above) and tags (pictured below) it also seems buggy that there is a minimum width on chips once there is more than one. That minimum width takes up unnecessary real-estate - especially as seen in the above example.

In tags:

The truncation of ‘enhancement’ is good, but the extra width of ‘form’ is not necessary.

It should be max-width instead of min-width, in the CSS. Then it would look like this:

For custom fields, taking out the min-width - then this takes care of the unnecessary [+1] also (compare to the picture at the top):

[lpb]

@Forum-team, Is there any chance this could be escalating and maybe the simple CSS change @Sarah_L suggests might be warranted (maybe just a typo originally?). Also, maybe if someone can look at the original confusion from the earlier posts too and confirm; maybe that was fixed??

And if you feel it would be better not to comingle the new reports with the old ones, we first could ask Sarah to start a separate English Forum > Product Feedback topic.

Thanks,

Larry

[Joanna_Czarnobilska]

Hello Everyone,
thank you for all your comments and in depth expertise.
I have escalated it for the product team to have a look into!

[Joanna_Czarnobilska]

Hello @lpb , and a happy new year!

I have a bit of an update here. Firstly, a change to the trunkation code was made, so you should already see an improvement on that front.
As for removing the min-width property, that approach was tested and evaluated, but the drawback of such an approach over the truncation approach is that, with a large number of pills, it is not possible to see the content of each pill. The current behaviour of custom field multiselect fields should properly use all the available width of the column to show as many pills as possible.

Thanks again for flagging this!

[lpb]

Thanks so much, @Joanna_Czarnobilska, and Happy New Year!

That sounds good, and interested to see if it works well for @Sarah_L.

Much appreciated,

Larry