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

[GH-ISSUE #2936] [Bug]: Transaction table constantly resizing #90799

New Issue
Closed
opened 2026-05-25 20:32:03 -05:00 by GiteaMirror · 16 comments
GiteaMirror commented 2026-05-25 20:32:03 -05:00
Owner
Copy Link

Originally created by @matt-fidd on GitHub (Jun 25, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2936

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

This is a really strange one, it only seems to happen on a single browser, but is reproducible for me on there. However it does not occur with the exact same budget file, on Chrome on a different computer.

Only occurs when viewing a single accounts table, none of the other accounts or tables.

I’ve not been able to create a test budget that reproduces the issue.

There is no logging in the console

https://github.com/actualbudget/actual/assets/81489167/671a3e37-c19a-464d-abcb-a528800eab8e

https://github.com/actualbudget/actual/assets/81489167/fb9b68b8-87a6-47d6-a4c7-38f923fb1be3

https://github.com/actualbudget/actual/assets/81489167/82150697-92d7-4b7f-aaf5-9bf6787008bf

Environment:

  • Windows 8.1 inside corporate VMWare
  • Chrome V109.0.5414.141 (32 bit)
  • Actual Edge

Where are you hosting Actual?

Locally via Yarn

What browsers are you seeing the problem on?

Chrome

Operating System

Other

Originally created by @matt-fidd on GitHub (Jun 25, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/2936 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? This is a really strange one, it only seems to happen on a single browser, but is reproducible for me on there. However it does not occur with the exact same budget file, on Chrome on a different computer. Only occurs when viewing a single accounts table, none of the other accounts or tables. I’ve not been able to create a test budget that reproduces the issue. There is no logging in the console https://github.com/actualbudget/actual/assets/81489167/671a3e37-c19a-464d-abcb-a528800eab8e https://github.com/actualbudget/actual/assets/81489167/fb9b68b8-87a6-47d6-a4c7-38f923fb1be3 https://github.com/actualbudget/actual/assets/81489167/82150697-92d7-4b7f-aaf5-9bf6787008bf Environment: - Windows 8.1 inside corporate VMWare - Chrome V109.0.5414.141 (32 bit) - Actual Edge ### Where are you hosting Actual? Locally via Yarn ### What browsers are you seeing the problem on? Chrome ### Operating System Other
GiteaMirror added the buguser interfacetransactions labels 2026-05-25 20:32:05 -05:00
GiteaMirror commented 2026-05-25 20:32:08 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Jun 25, 2024):

Are you able to reproduce this on https://demo.actualbudget.org (latest tagged release)?

<!-- gh-comment-id:2189741360 --> @MatissJanis commented on GitHub (Jun 25, 2024): Are you able to reproduce this on https://demo.actualbudget.org (latest `tagged` release)?
GiteaMirror commented 2026-05-25 20:32:08 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Jun 25, 2024):

This is not reproducable on demo.

I've worked out what the trigger is. When there are too many transactions to fit on a single page the scroll bar appears. It looks like there must be a very niche edge case where it's just on the verge of needing the scroll bar, and so flicks between adding and removing it.

To reproduce:

  • Add just enough transactions to a blank account that one more will trigger the scroll bar
  • Add one more
  • If the screen size is just right (I imagine this is a very small window because it's only occured in a very specific environment for me) then the table will add and remove the scrollbar in a loop
  • Adding or removing a single transaction will stop this from occuring.

Edge:
https://github.com/actualbudget/actual/assets/81489167/e758d50d-bfff-435c-8b14-a9e4418a28e7

Demo:
https://github.com/actualbudget/actual/assets/81489167/cb5572a3-7a6d-4794-9550-3d2afb5cb70c

<!-- gh-comment-id:2189810544 --> @matt-fidd commented on GitHub (Jun 25, 2024): This is not reproducable on demo. I've worked out what the trigger is. When there are too many transactions to fit on a single page the scroll bar appears. It looks like there must be a very niche edge case where it's just on the verge of needing the scroll bar, and so flicks between adding and removing it. To reproduce: - Add just enough transactions to a blank account that one more will trigger the scroll bar - Add one more - If the screen size is just right (I imagine this is a very small window because it's only occured in a very specific environment for me) then the table will add and remove the scrollbar in a loop - Adding or removing a single transaction will stop this from occuring. Edge: https://github.com/actualbudget/actual/assets/81489167/e758d50d-bfff-435c-8b14-a9e4418a28e7 Demo: https://github.com/actualbudget/actual/assets/81489167/cb5572a3-7a6d-4794-9550-3d2afb5cb70c
GiteaMirror commented 2026-05-25 20:32:09 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Jun 25, 2024):

Possible root cause: https://github.com/actualbudget/actual/pull/2867

<!-- gh-comment-id:2189814315 --> @MatissJanis commented on GitHub (Jun 25, 2024): Possible root cause: https://github.com/actualbudget/actual/pull/2867
GiteaMirror commented 2026-05-25 20:32:09 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Jun 25, 2024):

Let me try reverting that PR and seeing if it persists, the 200ms cycle would make sense

<!-- gh-comment-id:2189817495 --> @matt-fidd commented on GitHub (Jun 25, 2024): Let me try reverting that PR and seeing if it persists, the 200ms cycle would make sense
GiteaMirror commented 2026-05-25 20:32:11 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Jun 25, 2024):

Possible root cause: #2867

You're dead on, reverting the commit fixed the bug

<!-- gh-comment-id:2189825183 --> @matt-fidd commented on GitHub (Jun 25, 2024): > Possible root cause: #2867 You're dead on, reverting the commit fixed the bug
GiteaMirror commented 2026-05-25 20:32:12 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Jun 25, 2024):

cc @lelemm FYI

<!-- gh-comment-id:2189830210 --> @MatissJanis commented on GitHub (Jun 25, 2024): cc @lelemm FYI
GiteaMirror commented 2026-05-25 20:32:16 -05:00
Author
Owner
Copy Link

@lelemm commented on GitHub (Jun 25, 2024):

omg. I will try to reproduce it

<!-- gh-comment-id:2190010145 --> @lelemm commented on GitHub (Jun 25, 2024): omg. I will try to reproduce it
GiteaMirror commented 2026-05-25 20:32:17 -05:00
Author
Owner
Copy Link

@lelemm commented on GitHub (Jun 25, 2024):

@matt-fidd can you tell me what resolution are you using on that machine and scale size?

<!-- gh-comment-id:2190016252 --> @lelemm commented on GitHub (Jun 25, 2024): @matt-fidd can you tell me what resolution are you using on that machine and scale size?
GiteaMirror commented 2026-05-25 20:32:20 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Jun 25, 2024):

Looks to be a viewport of 1920 x 937 but I can't seem to reproduce it outside of my work remote desktop, even with the same viewport size.

<!-- gh-comment-id:2190034370 --> @matt-fidd commented on GitHub (Jun 25, 2024): Looks to be a viewport of 1920 x 937 but I can't seem to reproduce it outside of my work remote desktop, even with the same viewport size.
GiteaMirror commented 2026-05-25 20:32:21 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Jun 25, 2024):

Aha! It's tied to the Chrome version, not so much the viewport.

I just tested in Chromium 1070081 and could reproduce it easily.

Official build for Windows:
https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/1070081/

Similar version for Mac but I can't test
https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Mac/1070019/

<!-- gh-comment-id:2190048983 --> @matt-fidd commented on GitHub (Jun 25, 2024): Aha! It's tied to the Chrome version, not so much the viewport. I just tested in Chromium 1070081 and could reproduce it easily. Official build for Windows: https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/1070081/ Similar version for Mac but I can't test https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Mac/1070019/
GiteaMirror commented 2026-05-25 20:32:22 -05:00
Author
Owner
Copy Link

@lelemm commented on GitHub (Jun 26, 2024):

nice, I will download it to test out

<!-- gh-comment-id:2190245779 --> @lelemm commented on GitHub (Jun 26, 2024): nice, I will download it to test out
GiteaMirror commented 2026-05-25 20:32:24 -05:00
Author
Owner
Copy Link

@lelemm commented on GitHub (Jun 26, 2024):

tried to replicate, no success yet. Tried with demo and my own budget

<!-- gh-comment-id:2190417957 --> @lelemm commented on GitHub (Jun 26, 2024): tried to replicate, no success yet. Tried with demo and my own budget
GiteaMirror commented 2026-05-25 20:32:25 -05:00
Author
Owner
Copy Link

@lelemm commented on GitHub (Jun 26, 2024):

Ok, I was able to reproduce it now.
The cause of this is the fact that the number of lines in the grid is size of the screen, so the app keeps adding the scrollbar and removing it.

<!-- gh-comment-id:2191496493 --> @lelemm commented on GitHub (Jun 26, 2024): Ok, I was able to reproduce it now. The cause of this is the fact that the number of lines in the grid is size of the screen, so the app keeps adding the scrollbar and removing it.
GiteaMirror commented 2026-05-25 20:32:28 -05:00
Author
Owner
Copy Link

@lelemm commented on GitHub (Jun 26, 2024):

Try this https://deploy-preview-2941.demo.actualbudget.org/ @matt-fidd
I was able to use the demo budget. You have to delete transactions from an account to fill the screen like this:
image

<!-- gh-comment-id:2191600588 --> @lelemm commented on GitHub (Jun 26, 2024): Try this https://deploy-preview-2941.demo.actualbudget.org/ @matt-fidd I was able to use the demo budget. You have to delete transactions from an account to fill the screen like this: ![image](https://github.com/actualbudget/actual/assets/15043428/a9372fc5-d8bc-477b-a927-8e9597b6140e)
GiteaMirror commented 2026-05-25 20:32:32 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Jun 26, 2024):

Thank you!

That looks to have done the trick, I'm just using a blank file with 24 transactions, that seems to be the right amount to fill my page.

<!-- gh-comment-id:2191617798 --> @matt-fidd commented on GitHub (Jun 26, 2024): Thank you! That looks to have done the trick, I'm just using a blank file with 24 transactions, that seems to be the right amount to fill my page.
GiteaMirror commented 2026-05-25 20:32:35 -05:00
Author
Owner
Copy Link

@lelemm commented on GitHub (Jun 26, 2024):

Nice @matt-fidd ! good news! :)

@MatissJanis can you review the PR? merge is frozen atm too

<!-- gh-comment-id:2191641120 --> @lelemm commented on GitHub (Jun 26, 2024): Nice @matt-fidd ! good news! :) @MatissJanis can you review the PR? merge is frozen atm too
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 transactions 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#90799
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?