github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-09 21:40:21 -05:00
Code Issues 1.6k Packages Projects Releases 55 Wiki Activity

[GH-ISSUE #5217] [Bug]: Splitting existing transaction causes UI glitches as splits disappear and reappear #28010

New Issue
Open
opened 2026-04-18 04:37:51 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-18 04:37:51 -05:00
Owner
Copy Link

Originally created by @Ditti4 on GitHub (Jun 21, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/5217

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

I'm not sure how to best summarize the issue, so excuse the awkward title. Splitting an existing transaction seems to cause some kind of synchronization weirdness and makes the UI glitch, as the split transactions disappear and reappear.

Once I'm done splitting the transactions, I'm also left with a 0.00 split transaction.

https://github.com/user-attachments/assets/32325703-1880-40bf-b5f0-d06a3058371d

Just for clarity, in the video I press enter after entering the amount and then I don't press or click anything at all (until you see my start typing again).

None of this happens when creating a new transaction as a split transaction straight away.

How can we reproduce the issue?

I've been able to reproduce this on the demo instance, but it's not as pronounced there, likely because the demo instance has much fewer transactions.

  1. Create a transaction as a non-split transaction
  2. Edit the transaction category to turn the transaction into a split transaction
  3. Enter the first split amount, press Enter
  4. Observe glitchy UI behavior

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox

Operating System

Linux

Originally created by @Ditti4 on GitHub (Jun 21, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/5217 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? I'm not sure how to best summarize the issue, so excuse the awkward title. Splitting an existing transaction seems to cause some kind of synchronization weirdness and makes the UI glitch, as the split transactions disappear and reappear. Once I'm done splitting the transactions, I'm also left with a 0.00 split transaction. https://github.com/user-attachments/assets/32325703-1880-40bf-b5f0-d06a3058371d Just for clarity, in the video I press enter after entering the amount and then I don't press or click anything at all (until you see my start typing again). None of this happens when creating a new transaction as a split transaction straight away. ### How can we reproduce the issue? I've been able to reproduce this on the demo instance, but it's not as pronounced there, likely because the demo instance has much fewer transactions. 1. Create a transaction as a non-split transaction 2. Edit the transaction category to turn the transaction into a split transaction 3. Enter the first split amount, press Enter 4. Observe glitchy UI behavior ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Firefox ### Operating System Linux
GiteaMirror added the help wanteduser interfacegood first issuebug labels 2026-04-18 04:37:51 -05:00
GiteaMirror commented 2026-04-18 04:37:54 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Jun 21, 2025):

I can see it, but on my machine its basically instant after making the second line.

<!-- gh-comment-id:2993795238 --> @youngcw commented on GitHub (Jun 21, 2025): I can see it, but on my machine its basically instant after making the second line.
GiteaMirror commented 2026-04-18 04:37:54 -05:00
Author
Owner
Copy Link

@Ditti4 commented on GitHub (Jun 22, 2025):

I don't know much about the code here, but could it simply be related to the number of (split) transactions that I've got in my instance?

My wife and I have been budgeting (first using YNAB4, then Actual) for at least five years and have amassed a few thousand transactions over this time. We also diligently use the splits for e.g. grocery store transactions when they contain pet food, toiletries, ... - something that's probably not done by many people. 😄

<!-- gh-comment-id:2994068504 --> @Ditti4 commented on GitHub (Jun 22, 2025): I don't know much about the code here, but could it simply be related to the number of (split) transactions that I've got in my instance? My wife and I have been budgeting (first using YNAB4, then Actual) for at least five years and have amassed a few thousand transactions over this time. We also diligently use the splits for e.g. grocery store transactions when they contain pet food, toiletries, ... - something that's probably not done by many people. 😄
GiteaMirror commented 2026-04-18 04:37:55 -05:00
Author
Owner
Copy Link

@chill commented on GitHub (Jun 22, 2025):

I have the same behaviour, happens across Mac and Windows, both in Chrome. I also have a large number of splits and a long transaction history. The behaviour repeats multiple times if using the "distribute" button too - the different split lines will be filled out automatically, then disappear, be re-added, be re-filled, and eventually it stabilises and I can carry on using the UI.

<!-- gh-comment-id:2994222718 --> @chill commented on GitHub (Jun 22, 2025): I have the same behaviour, happens across Mac and Windows, both in Chrome. I also have a large number of splits and a long transaction history. The behaviour repeats multiple times if using the "distribute" button too - the different split lines will be filled out automatically, then disappear, be re-added, be re-filled, and eventually it stabilises and I can carry on using the UI.
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 good first issue help wanted user interface
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#28010
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?