Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attachment chip exceeds desirable width #193

Open
asuwebdesign opened this issue Oct 7, 2024 · 1 comment · May be fixed by #261
Open

Attachment chip exceeds desirable width #193

asuwebdesign opened this issue Oct 7, 2024 · 1 comment · May be fixed by #261
Assignees
Labels
bug Something isn't working v6.x Applies to only the PF6 version
Milestone

Comments

@asuwebdesign
Copy link
Collaborator

If you attach a file with a long file name, the attachment chip will try to render the entirety of the name. This can potentially break layouts and isn't desirable, especially in scenarios where the chatbot needs to support multiple file attachments. Let's apply a truncation rule on the file name in the chip.

For overlay and dock mode, try to cap the width of each attachment chip to roughly 50% of the message bar. Take into account a gap between each chip (if more than 1 attached). Width might vary depending on the rendered size of the chatbot.

For fullscreen mode, and as the chatbot and message bar get wider, simply cap the width of the chip to 224px (14rem).
Image

@asuwebdesign asuwebdesign added bug Something isn't working v6.x Applies to only the PF6 version labels Oct 7, 2024
@rebeccaalpert
Copy link
Member

That's valid!

@rebeccaalpert rebeccaalpert added this to the 2024.Q4 milestone Oct 7, 2024
@rebeccaalpert rebeccaalpert self-assigned this Oct 18, 2024
@rebeccaalpert rebeccaalpert linked a pull request Oct 22, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working v6.x Applies to only the PF6 version
Projects
Status: PR Review
Development

Successfully merging a pull request may close this issue.

2 participants