github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 07:04:23 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #6213] [Bug]: down-arrow key not working in cover-overspending-popup #72383

New Issue
Closed
opened 2026-05-16 12:25:47 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-16 12:25:47 -05:00
Owner
Copy Link

Originally created by @Mansarde on GitHub (Nov 20, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6213

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

In previous versions, when clicking on a negative value in the budget, I'd usually continue with the keyboard to quickly select a category to cover the overspending.

Unfortunately in the latest version (v25.11.0) once the popup shows where you have to choose a category, pressing the arrow-down button on the keyboard doesn't select the first category anymore.
I now have to either start typing letters in the search field or hover the mouse over the list before I can use the arrow-buttons for movement again.

In previous versions pressing the arrow-down button worked even if I didn't type anything in the search box or hovered the mouse over the list.
This way I was able to quickly select the very first entry (i.e. "To Budget").

How can we reproduce the issue?

  1. Create a negative value in a category.
  2. Go to the buget screen.
  3. Make sure there is a positive "To Budget " balance.
  4. With the mouse, click on the negative category balance to open the popup menu.
  5. With the keyboard, press the arrow-down button to select "Cover Overspending", then press ENTER.
  6. In the following category list that pops up, try to press the arrow-down button.
    => Notice how that has no effect.

Expected Result:
Pressing the arrow-down button in step 7 should select the first entry in the list (as previous verions did).

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome

Operating System

Windows 11

Originally created by @Mansarde on GitHub (Nov 20, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/6213 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? In previous versions, when clicking on a negative value in the budget, I'd usually continue with the keyboard to quickly select a category to cover the overspending. Unfortunately in the latest version (v25.11.0) once the popup shows where you have to choose a category, pressing the arrow-down button on the keyboard doesn't select the first category anymore. I now have to either start typing letters in the search field or hover the mouse over the list before I can use the arrow-buttons for movement again. In previous versions pressing the arrow-down button worked even if I didn't type anything in the search box or hovered the mouse over the list. This way I was able to quickly select the very first entry (i.e. "To Budget"). ### How can we reproduce the issue? 1. Create a negative value in a category. 2. Go to the buget screen. 3. Make sure there is a positive "To Budget " balance. 4. With the mouse, click on the negative category balance to open the popup menu. 5. With the keyboard, press the arrow-down button to select "Cover Overspending", then press ENTER. 6. In the following category list that pops up, try to press the arrow-down button. => Notice how that has no effect. Expected Result: Pressing the arrow-down button in step 7 should select the first entry in the list (as previous verions did). ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome ### Operating System Windows 11
GiteaMirror added the needs infobug labels 2026-05-16 12:25:47 -05:00
GiteaMirror commented 2026-05-16 12:25:51 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Nov 20, 2025):

👋 Are you able to reproduce this on edge? It seems to be working fine for me.

<!-- gh-comment-id:3560085554 --> @MatissJanis commented on GitHub (Nov 20, 2025): 👋 Are you able to reproduce this on [edge](https://edge.actualbudget.org/budget)? It seems to be working fine for me.
GiteaMirror commented 2026-05-16 12:25:51 -05:00
Author
Owner
Copy Link

@Mansarde commented on GitHub (Nov 26, 2025):

👋 Are you able to reproduce this on edge? It seems to be working fine for me.

I've tried it on the latest edge version and it works over there.
But I think that's because the "cover overspending" dialog changed a bit.

Currently once the dialog pops up, there's only the "from" field.
But in the edge version there's also an "amount" field above that, which is pre-selected.

So where previously you were able to just press down-arrow to select the first element in the "from" field, in the edge version you have to first hit TAB and then you can press down-arrow for the "from" field.
Which works, I guess, but my workflow to cover overspending from the "To be budgeted" field was to have one hand on the mouse to click on each negative balance in the budget and then use the other hand to press down-enter-down-enter.

With the new dialog I either have to move the hand all the way over to the TAB key or keep the left hand on that key and instead move the right hand between the arrow/enter key and the mouse.

Sounds ridiculous if I describe it like that, but it was just a nice and fast workflow for me.
With that new "amount" field that will have to change though. Ah well, not too bad, I'll adapt. :)

But I guess this makes the issue obsolete then.
Thanks and have a nice day! ✌️

<!-- gh-comment-id:3582373247 --> @Mansarde commented on GitHub (Nov 26, 2025): > 👋 Are you able to reproduce this on [edge](https://edge.actualbudget.org/budget)? It seems to be working fine for me. I've tried it on the latest edge version and it works over there. But I think that's because the "cover overspending" dialog changed a bit. Currently once the dialog pops up, there's only the "from" field. But in the edge version there's also an "amount" field above that, which is pre-selected. So where previously you were able to just press down-arrow to select the first element in the "from" field, in the edge version you have to first hit TAB and then you can press down-arrow for the "from" field. Which works, I guess, but my workflow to cover overspending from the "To be budgeted" field was to have one hand on the mouse to click on each negative balance in the budget and then use the other hand to press down-enter-down-enter. With the new dialog I either have to move the hand all the way over to the TAB key or keep the left hand on that key and instead move the right hand between the arrow/enter key and the mouse. Sounds ridiculous if I describe it like that, but it was just a nice and fast workflow for me. With that new "amount" field that will have to change though. Ah well, not too bad, I'll adapt. :) But I guess this makes the issue obsolete then. Thanks and have a nice day! ✌️
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug needs info
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#72383
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?