[GH-ISSUE #7981] [Bug]: Split transaction remaining balance popover overflows horizontally and gets stuck across different browsers #117633

Open
opened 2026-06-11 13:04:04 -05:00 by GiteaMirror · 5 comments
Owner

Originally created by @kryll on GitHub (May 28, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7981

What happened?

Describe the bug
When splitting a transaction, the popover/tooltip that manages the remaining amount overflows the screen horizontally on the right side, hiding the action buttons.

Critical update: This issue completely breaks the transaction state and synchronizes across devices/browsers. After getting stuck in Google Chrome, I opened the app in Mozilla Firefox, and the exact same broken split transaction and cut-off UI element were still there. This means the corrupted/incomplete split state is being saved to the database and synced, making it impossible to clear or cancel the operation even after refreshing or switching browsers.

Screenshots

Image

Environment:

Actual Budget Version: v26.5.2

Browser / App: Google Chrome & Mozilla Firefox

How can we reproduce the issue?

  1. Go to the Transactions page.

  2. Click on an existing transaction and select Split (Dividir).

  3. Notice the popover handling the remaining funds is cut off horizontally on the right edge.

  4. Refresh the page or open the application in a completely different browser (e.g., switch from Chrome to Firefox).

  5. The broken split state and the unclickable popover persist.

Where are you hosting Actual?

Locally via Yarn

What browsers are you seeing the problem on?

Chrome

Operating System

Windows 11

Originally created by @kryll on GitHub (May 28, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7981 ### What happened? **Describe the bug** When splitting a transaction, the popover/tooltip that manages the remaining amount overflows the screen horizontally on the right side, hiding the action buttons. Critical update: This issue completely breaks the transaction state and synchronizes across devices/browsers. After getting stuck in Google Chrome, I opened the app in Mozilla Firefox, and the exact same broken split transaction and cut-off UI element were still there. This means the corrupted/incomplete split state is being saved to the database and synced, making it impossible to clear or cancel the operation even after refreshing or switching browsers. Screenshots <img width="1700" height="106" alt="Image" src="https://github.com/user-attachments/assets/8c5b05f9-b9a3-4a0e-8a8e-914e935da7fc" /> **Environment:** Actual Budget Version: v26.5.2 Browser / App: Google Chrome & Mozilla Firefox ### How can we reproduce the issue? 1. Go to the Transactions page. 2. Click on an existing transaction and select Split (Dividir). 3. Notice the popover handling the remaining funds is cut off horizontally on the right edge. 4. Refresh the page or open the application in a completely different browser (e.g., switch from Chrome to Firefox). 5. The broken split state and the unclickable popover persist. ### Where are you hosting Actual? Locally via Yarn ### What browsers are you seeing the problem on? Chrome ### Operating System Windows 11
GiteaMirror added the bug label 2026-06-11 13:04:04 -05:00
Author
Owner

@coderabbitai[bot] commented on GitHub (May 28, 2026):

⚠️ Possible Duplicate Issue(s)
🔗 Related PRs

actualbudget/actual#7814 - Fix split transaction popover wrapping [merged]


📝 Issue Planner

Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

  • Create Plan

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

<!-- gh-comment-id:4562073794 --> @coderabbitai[bot] commented on GitHub (May 28, 2026): <!-- This is an auto-generated issue plan by CodeRabbit --> <details> <summary>⚠️ Possible Duplicate Issue(s)</summary> - https://github.com/actualbudget/actual/issues/7738 </details> <details> <summary>🔗 Related PRs</summary> actualbudget/actual#7814 - Fix split transaction popover wrapping [merged] </details> --- <details> <summary>📝 Issue Planner</summary> <sub>Check the box below or use the `@coderabbitai plan` command to generate an implementation plan and prompts that you can use with your favorite coding assistant.</sub> - [ ] <!-- {"checkboxId": "8d4f2b9c-3e1a-4f7c-a9b2-d5e8f1c4a7b9"} --> Create Plan </details> --- <details> <summary> 🧪 Issue enrichment is currently in open beta.</summary> You can configure auto-planning by selecting labels in the issue_enrichment configuration. To disable automatic issue enrichment, add the following to your `.coderabbit.yaml`: ```yaml issue_enrichment: auto_enrich: enabled: false ``` </details> 💬 Have feedback or questions? Drop into our [discord](https://discord.gg/coderabbit)!
Author
Owner

@kryll commented on GitHub (May 28, 2026):

I am experiencing this exact same issue on v26.5.2. The remaining balance popover overflows horizontally on the right edge of the screen, completely hiding the action buttons.

After troubleshooting, I found a couple of critical clues that might help pinpoint the root cause:

  1. It is account-specific: This bug ONLY happens when trying to split transactions inside one specific account. If I try to split transactions in any other account in my budget, the popover aligns correctly and works perfectly. This suggests it might be related to how specific column widths or table layouts are saved/configured for that particular account, pushing the React layout engine out of bounds.
  2. It persists across browsers and refreshes: Once the split gets stuck in this broken UI state, refreshing the page does not fix it. Furthermore, switching from Google Chrome to Mozilla Firefox displays the exact same frozen, broken layout. This means this incomplete/broken split state is being saved to the database and synchronized, making it impossible to clear or cancel the operation.
<!-- gh-comment-id:4563177295 --> @kryll commented on GitHub (May 28, 2026): I am experiencing this exact same issue on **v26.5.2**. The remaining balance popover overflows horizontally on the right edge of the screen, completely hiding the action buttons. After troubleshooting, I found a couple of critical clues that might help pinpoint the root cause: 1. **It is account-specific:** This bug ONLY happens when trying to split transactions inside one specific account. If I try to split transactions in any other account in my budget, the popover aligns correctly and works perfectly. This suggests it might be related to how specific column widths or table layouts are saved/configured for that particular account, pushing the React layout engine out of bounds. 2. **It persists across browsers and refreshes:** Once the split gets stuck in this broken UI state, refreshing the page does not fix it. Furthermore, switching from Google Chrome to Mozilla Firefox displays the exact same frozen, broken layout. This means this incomplete/broken split state is being saved to the database and synchronized, making it impossible to clear or cancel the operation.
Author
Owner

@youngcw commented on GitHub (May 29, 2026):

Have you tested https://nightly.actualbudget.org? This maybe have been fixed already

<!-- gh-comment-id:4577283298 --> @youngcw commented on GitHub (May 29, 2026): Have you tested https://nightly.actualbudget.org? This maybe have been fixed already
Author
Owner

@cculbertson81 commented on GitHub (Jun 2, 2026):

Have you tested https://nightly.actualbudget.org? This maybe have been fixed already

I'm still seeing this issue as of the v26.6.0 release.

<!-- gh-comment-id:4607181851 --> @cculbertson81 commented on GitHub (Jun 2, 2026): > Have you tested https://nightly.actualbudget.org? This maybe have been fixed already I'm still seeing this issue as of the v26.6.0 release.
Author
Owner

@Sarke commented on GitHub (Jun 8, 2026):

I'm seeing this too on Firefox. Popover element has max-height: 0, removing this makes it look normal.

<!-- gh-comment-id:4645160592 --> @Sarke commented on GitHub (Jun 8, 2026): I'm seeing this too on Firefox. Popover element has `max-height: 0`, removing this makes it look normal.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#117633