The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: getdave <get_dave@git.wordpress.org>
Co-authored-by: ntsekouras <ntsekouras@git.wordpress.org>
Co-authored-by: jameskoster <jameskoster@git.wordpress.org>
Co-authored-by: jasmussen <joen@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Size Change: -1 B (0%)

Total Size: 1.75 MB

_{compressed-size-action}

Thank you for the PR, it would certainly be good to address this, but I'm not sure adding padding is the way to go. Mostly because it doesn't stop the text from wrapping, which I consider to be the biggest offender here – it makes the chip difficult to interpret at a glance.

Ideally the full text would appear on a single line like so:

If there's a reliable way to do that then it could be worth merging as a short-term solution. But it's going to get a bit tricky down the road if the filter is multi-select and has many values, e.g. Author is any: Twenty Twenty-Four, Twenty Twenty-Three, Twenty Twenty-Two. Or if the value itself is very long, e.g. Title contains: "A very long value that I want to find across all my post titles".

We probably need a more polished solution that solves these problems across all layouts. How should we handle extremely long chips like the examples above... should values truncate? Should multi-selections be simplified to e.g. Author is any: 3 selected. Should the row of scroll horizontally in List layout?

I'd echo Jay's instincts here, we should find ways to avoid the chip wrapping. Whether smaller font sizes, eliding text, etc. A bit of an out there solution that the Google app store employs is to marquee/scroll the text.

No problem and thanks for the good instincts. No wrapping approach sounds like a good goal.

One thing I've encountered with a similar situation I encountered during work on the Link UI - when you try and avoid wrapping and text strings get particularly long the instinct is to truncate the text. That's necessary to avoid overflowing. However there needs to be a means (perceivable to all) for users to access the full text.

I'll close this one out.

We can continue exploring treatments for the chips specifically in #59696. I opened a new issue for the display of many chips in list layout / narrow viewports: #60696