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

[GH-ISSUE #4801] [Bug]: UI nit in payment field when adding transactions and focus changes #16281

New Issue
Closed
opened 2026-04-14 19:23:54 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-14 19:23:54 -05:00
Owner
Copy Link

Originally created by @tfheen on GitHub (Apr 13, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4801

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

When manually entering a transaction, the payment field is pre-filled with "0,00" (or 0.00 depending on settings). When focus enters the payment field, the entire field is pre-selected, so entering a value will overwrite the value there, which is desireable. If one at that point (without at all interacting with the field) changes the focus to a different tab or window, the selection is no longer present when focus returns to the window with Actual in it, requiring the user to manually select the entire field or erase the 0,00 value present before entering the correct amount.

Would it be possible to either not prefill the value to 0 or preserve the selection on focus change?

How can we reproduce the issue?

  • Add new transaction, press tab four times
  • Switch focus to another window
  • Switch focus back
  • Observe that you need to manually erase/select the field.

Where are you hosting Actual?

Locally

What browsers are you seeing the problem on?

Chromium, I do not see this on Firefox.

Operating System

Debian Linux

Originally created by @tfheen on GitHub (Apr 13, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/4801 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? When manually entering a transaction, the payment field is pre-filled with "0,00" (or 0.00 depending on settings). When focus enters the payment field, the entire field is pre-selected, so entering a value will overwrite the value there, which is desireable. If one at that point (without at all interacting with the field) changes the focus to a different tab or window, the selection is no longer present when focus returns to the window with Actual in it, requiring the user to manually select the entire field or erase the 0,00 value present before entering the correct amount. Would it be possible to either not prefill the value to 0 or preserve the selection on focus change? ### How can we reproduce the issue? - Add new transaction, press tab four times - Switch focus to another window - Switch focus back - Observe that you need to manually erase/select the field. ### Where are you hosting Actual? Locally ### What browsers are you seeing the problem on? Chromium, I do not see this on Firefox. ### Operating System Debian Linux
GiteaMirror added the bug label 2026-04-14 19:23:54 -05:00
GiteaMirror commented 2026-04-14 19:23:55 -05:00
Author
Owner
Copy Link

@alecbakholdin commented on GitHub (May 1, 2025):

I can't reproduce this on Mac or Windows. When I tab out and back in, focus is preserved. This seems like it may be more of a browser issue than an Actual issue

<!-- gh-comment-id:2845807609 --> @alecbakholdin commented on GitHub (May 1, 2025): I can't reproduce this on Mac or Windows. When I tab out and back in, focus is preserved. This seems like it may be more of a browser issue than an Actual issue
GiteaMirror commented 2026-04-14 19:23:56 -05:00
Author
Owner
Copy Link

@tfheen commented on GitHub (May 2, 2025):

I can reproduce this on Chrome on ChromeOS, Firefox v138 on MacOS (Monterey), Chrome 135 on MacOS (Monterey) in addition to the original report. It does not reproduce for me in Safari on MacOS Monterey.

After poking at this a little bit, I found a hint what might be contributing: I'm in a locale that uses "," as the comma separator.

The steps to reproduce:

  • Go to an account (I'm using an on budget one, I don't think that part matters)
  • Click "add new"
  • Press tab four times (until focus is on the "Payment" field)
  • Observe that the entire 0.00 field is selected so that any text input will replace the field contents.
  • Press command-tab to switch to another application
  • Press command-tab to switch back
  • Observe that the Payment field is now 0,00, and the selection has disappeared and the cursor is at the end of the input field.

This is with 25.4.0 running from Docker.

With Safari, the payment field does not change to "0,00" when switching focus back and forth.

<!-- gh-comment-id:2847578552 --> @tfheen commented on GitHub (May 2, 2025): I can reproduce this on Chrome on ChromeOS, Firefox v138 on MacOS (Monterey), Chrome 135 on MacOS (Monterey) in addition to the original report. It does not reproduce for me in Safari on MacOS Monterey. After poking at this a little bit, I found a hint what might be contributing: I'm in a locale that uses "," as the comma separator. The steps to reproduce: - Go to an account (I'm using an on budget one, I don't think that part matters) - Click "add new" - Press tab four times (until focus is on the "Payment" field) - Observe that the entire 0.00 field is selected so that any text input will replace the field contents. - Press command-tab to switch to another application - Press command-tab to switch back - Observe that the Payment field is now 0,00, and the selection has disappeared and the cursor is at the end of the input field. This is with 25.4.0 running from Docker. With Safari, the payment field does not change to "0,00" when switching focus back and forth.
GiteaMirror commented 2026-04-14 19:23:56 -05:00
Author
Owner
Copy Link

@alecbakholdin commented on GitHub (May 2, 2025):

@tfheen It was the comma decimal separator! We set a default value of '0.00' for the amount fields, which when you alt tabbed would update to '0,00' (period -> comma). Since the text changed, it would get deselected. That should be resolved in the linked PR. Thank you!

<!-- gh-comment-id:2848172113 --> @alecbakholdin commented on GitHub (May 2, 2025): @tfheen It was the comma decimal separator! We set a default value of '0.00' for the amount fields, which when you alt tabbed would update to '0,00' (period -> comma). Since the text changed, it would get deselected. That should be resolved in the linked PR. Thank you!
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#16281
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?