[Bug]: Down arrow key no longer selects category #2724

New Issue

GiteaMirror · 2026-02-28T20:25:46-06:00

GiteaMirror commented

2026-02-28 20:25:46 -06:00

Originally created by @ethw on GitHub (Dec 14, 2025).

Verified issue does not already exist?

I have searched and found no existing issue

What happened?

Usually to enter a transaction I click "Add new", and then I use my keyboard (tab + arrow keys) to fill in all the fields.

After a recent update pressing the "down arrow" key no longer lets you select the category. This means I need to use my mouse to select category which is much slower.

Filing as bug instead of feature request because I am 99% sure this worked in the past.

Client/server version v25.12.0

How can we reproduce the issue?

On a PC

Go to account view
Click "Add new"
Tab over to "Category" field
Press down arrow -> Notice that the first category in the list was not selected after pressing down arrow

Expected behaviour: First down arrow press selects "Split Transaction", second press selects the first category, third press selects second category, and so on.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox
Chrome

Operating System

Windows 11

Originally created by @ethw on GitHub (Dec 14, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? Usually to enter a transaction I click "Add new", and then I use my keyboard (tab + arrow keys) to fill in all the fields. After a recent update pressing the "down arrow" key no longer lets you select the category. This means I need to use my mouse to select category which is much slower. Filing as bug instead of feature request because I am 99% sure this worked in the past. Client/server version `v25.12.0` ### How can we reproduce the issue? On a PC 1. Go to account view 2. Click "Add new" 3. Tab over to "Category" field 4. Press down arrow -> Notice that the first category in the list was not selected after pressing down arrow Expected behaviour: First down arrow press selects "Split Transaction", second press selects the first category, third press selects second category, and so on. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? - Firefox - Chrome ### Operating System Windows 11

GiteaMirror added the transactions regression good first issue bug help wanted labels 2026-02-28 20:25:46 -06:00

GiteaMirror commented

2026-02-28 20:25:47 -06:00

@danielkubica commented on GitHub (Dec 15, 2025):

I can confirm. I had the same workflow with the tab + arrow keys for entering transactions, but after the recent update I can't select the category with the up/down arrow key. I have to select it either with the mouse (slow), or press space and backspace, after which the arrow keys work again (which isn't a real solution).

I am also hosting Actual with docker, using version v25.12.0.
Browser - Firefox

@danielkubica commented on GitHub (Dec 15, 2025): I can confirm. I had the same workflow with the tab + arrow keys for entering transactions, but after the recent update I can't select the category with the up/down arrow key. I have to select it either with the mouse (slow), or press space and backspace, after which the arrow keys work again (which isn't a real solution). I am also hosting Actual with docker, using version v25.12.0. Browser - Firefox

GiteaMirror commented

2026-02-28 20:25:48 -06:00

@lucioperez01 commented on GitHub (Dec 17, 2025):

I'm working on this issue

@lucioperez01 commented on GitHub (Dec 17, 2025): I'm working on this issue

GiteaMirror commented

2026-02-28 20:25:48 -06:00

@MohtashimAli85 commented on GitHub (Feb 2, 2026):

Same on account dropdown arrow up down not working,
please fix it, its annoying

@MohtashimAli85 commented on GitHub (Feb 2, 2026): Same on account dropdown arrow up down not working, please fix it, its annoying

GiteaMirror commented

2026-02-28 20:25:48 -06:00

@crdavis12 commented on GitHub (Feb 24, 2026):

Bump on this issue. Looks like a couple of stalled PRs but can confirm it is still present.

@crdavis12 commented on GitHub (Feb 24, 2026): Bump on this issue. Looks like a couple of stalled PRs but can confirm it is still present.

GiteaMirror commented

2026-02-28 20:25:49 -06:00

@db-src commented on GitHub (Feb 27, 2026):

'Bumping' achieves nothing, except annoying other people. Yes, it's still present, hence the bug still being open.

@db-src commented on GitHub (Feb 27, 2026): 'Bumping' achieves nothing, except annoying other people. Yes, it's still present, hence the bug still being open.