github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-05 22:52:20 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[GH-ISSUE #940] [Bug]: Inconsistent ledger scrolling when using keyboard shortcuts #7305

New Issue
Closed
opened 2026-04-10 17:04:17 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-10 17:04:17 -05:00
Owner
Copy Link

Originally created by @youngcw on GitHub (Apr 23, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/940

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

If I navigate a ledger using j/k the ledger moves in an expected way, but when using down/up arrows the ledger tries to move faster than the highlighted transaction moves. This causes jumpy motion sometimes, or it causes the highlighted transaction to be out of the visible range.

To replicate:

  1. Open an account ledger with lots of transactions. The "Bank of America" demo account works to test.
  2. click a transaction check box to allow keyboard shortcuts
  3. hold the down arrow and watch the ledger move too fast.

Compare against j/k scrolling which works fine (will need a build that wasn't broken with j/k). The visible range only changes when you reach the edge, and doesn't move with every press of j/k where with down/up the ledger moves every key press.

Ive also noticed that in Chrome the ledger will jump when the highlighted trans is out of range (so not as much of an issue), but that doesn't happen in Firefox.

What error did you receive?

No response

Where are you hosting Actual?

NAS

What browsers are you seeing the problem on?

Firefox, Chrome

Operating System

Linux

Originally created by @youngcw on GitHub (Apr 23, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/940 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? If I navigate a ledger using j/k the ledger moves in an expected way, but when using down/up arrows the ledger tries to move faster than the highlighted transaction moves. This causes jumpy motion sometimes, or it causes the highlighted transaction to be out of the visible range. To replicate: 1. Open an account ledger with lots of transactions. The "Bank of America" demo account works to test. 2. click a transaction check box to allow keyboard shortcuts 3. hold the down arrow and watch the ledger move too fast. Compare against j/k scrolling which works fine (will need a build that wasn't broken with j/k). The visible range only changes when you reach the edge, and doesn't move with every press of j/k where with down/up the ledger moves every key press. Ive also noticed that in Chrome the ledger will jump when the highlighted trans is out of range (so not as much of an issue), but that doesn't happen in Firefox. ### What error did you receive? _No response_ ### Where are you hosting Actual? NAS ### What browsers are you seeing the problem on? Firefox, Chrome ### Operating System Linux
GiteaMirror added the bug label 2026-04-10 17:04:17 -05:00
GiteaMirror commented 2026-04-10 17:04:19 -05:00
Author
Owner
Copy Link

@aaroneiche commented on GitHub (Apr 25, 2023):

I've noticed this as well when I first installed Actual. The arrow keys are both moving to the next checkbox as well as issuing a scroll event relative to the overflow. This is a spot where we need to exercise caution - messing with how scrolling works might confuse a large audience.

Maybe when a checkbox is selected it could change the scroll behavior?

<!-- gh-comment-id:1521189067 --> @aaroneiche commented on GitHub (Apr 25, 2023): I've noticed this as well when I first installed Actual. The arrow keys are both moving to the next checkbox as well as issuing a scroll event relative to the overflow. This is a spot where we need to exercise caution - messing with how scrolling works might confuse a large audience. Maybe when a checkbox is selected it could change the scroll behavior?
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
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug
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#7305
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?