[Bug] Composer attachment remove button not reachable by keyboard (a11y)
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- tauri, typescript
- Domain
- accessibility, desktop, frontend
Research direction
Open ComposerAttachments.tsx and compare the remove controls for the generic file chip and image/video thumbnail with the always-visible upload-cancel button. Reproduce the issue in the desktop app using only the keyboard, then verify that each attachment remove button becomes reachable and activatable without hovering.
Written by the indexing model from the issue text.
Description
Describe the bug
The "remove" (×) button on message composer attachments (both the generic
file chip and the image/video thumbnail) only appears on mouse hover
(hidden group-hover:flex in ComposerAttachments.tsx). Since the button is
display: none until hover, it's removed from the tab order entirely —
there's no way to reach or activate it with the keyboard.
To Reproduce:
- Open the message composer and attach a file (or image).
- Tab through the composer without touching the mouse.
- Try to remove the attachment using only the keyboard.
Expected behavior:
The remove button should be reachable via keyboard, e.g. by also showing it
on focus-within (group-focus-within:flex), not just on hover.
Supporting Material
Screenshot attached — attachment chip with remove button only visible via
hover.
Environment:
- Desktop app (Tauri)
Additional context
Compare with the upload-cancel button in the same file
(ComposerAttachments.tsx, upload placeholder), which is always visible/focusable
and doesn't have this issue.
- Dominant language
- Rust
- Stars
- 33.7k
- Forks
- 4.4k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 239
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from block/buzz
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
workflow_sink's mention parser never masks code regions — @name inside a code span wakes the agent Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 Half a day Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug team:backend track:services-maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cowprotocol/services#4950 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·