[Bug]: Thread actions menu is silent in NVDA browse mode in the desktop app
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- electron, typescript
- Domain
- accessibility, desktop
Research direction
Start in the desktop app area at apps/desktop and trace how the chat header's thread actions button opens its menu. Reproduce the steps on Windows with NVDA in browse mode, then compare the menu behavior with the minimal Electron 44.10.1 reproduction described in the issue. Done means NVDA announces and navigates the first menu item with the arrow keys without manually switching to focus mode.
Written by the indexing model from the issue text.
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/desktop
Steps to reproduce
- On Windows, run NVDA and open the T3 Code desktop app.
- Open a thread.
- In browse mode, move to the "Thread actions for <title>" button in the chat header.
- Press Enter.
- Press Down.
Expected behavior
NVDA announces the first item of the thread actions menu, and the arrow keys move through the menu without switching modes by hand.
Actual behavior
NVDA says nothing when the menu opens. The menu is open, but no item is selected and NVDA stays in browse mode, so Down moves the browse cursor through the page behind the menu instead of through the menu.
The menu can only be reached by switching to focus mode by hand.
The same happens in a minimal Electron 44.10.1 app that opens a native menu from a button click, tested with NVDA 2026.3.1:
| Step, starting in browse mode | NVDA says |
|---|---|
| Enter on the button | nothing |
| Down | the next paragraph on the page |
| NVDA+Space, then Down | "Rename 1 of 3" |
Impact
Minor bug or occasional failure
Version or commit
0.1.10-nightly.20261112.4564
Environment
Windows 11, T3 Code desktop (Nightly), NVDA
Workaround
Press NVDA+Space to switch to focus mode, then press Down. NVDA then reads the first menu item and the arrow keys work.
- Dominant language
- TypeScript
- Stars
- 24.8k
- Forks
- 6.4k
- Avg merge
- 4h 16m
- Merged PRs (30d)
- 352
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 pingdotgg/t3code
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
All issues in pingdotgg/t3code
Similar issues
-
Autocomplete still accepts an option after becoming disabledPossibly taken @Xapollon430 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
reduxjs/react-redux#2416 · 1 comment ·