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

[GH-ISSUE #7667] [Bug]: When on the web app and I have the window in width where I can only see one month at a time, then the "cover overspending" drop down does not want to open. #80584

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

Originally created by @ZainAjam on GitHub (Apr 30, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7667

What happened?

i was trying open the "cover overspending" selection menu for an overspent budgeted item when the width of the web window was only wide enough to show one month in a view, and the menu won't appear. I have to maximise the window or make it big enough so at least 2 months show in a view before the "cover overspending" menu will show up.

here is a video of what happens when I'm trying to open the "cover overspending" menu while the web window is only wide enough to show one month in the budget view.

https://github.com/user-attachments/assets/ae96429e-c304-4a09-a66e-fcf1ec95a40e

How can we reproduce the issue?

  1. Open the actualbudget web app but only open the window as wide to see one budget month in a view (e.g. half a screen wide)
  2. Look for a budget item that is overspent
  3. Click on the overspent amount in the last column
  4. Click on "cover overspending"
  5. Note that the menu won't show.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome, Microsoft Edge

Operating System

Windows 11

Originally created by @ZainAjam on GitHub (Apr 30, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7667 ### What happened? i was trying open the "cover overspending" selection menu for an overspent budgeted item when the width of the web window was only wide enough to show one month in a view, and the menu won't appear. I have to maximise the window or make it big enough so at least 2 months show in a view before the "cover overspending" menu will show up. here is a video of what happens when I'm trying to open the "cover overspending" menu while the web window is only wide enough to show one month in the budget view. https://github.com/user-attachments/assets/ae96429e-c304-4a09-a66e-fcf1ec95a40e ### How can we reproduce the issue? 1. Open the actualbudget web app but only open the window as wide to see one budget month in a view (e.g. half a screen wide) 2. Look for a budget item that is overspent 3. Click on the overspent amount in the last column 4. Click on "cover overspending" 5. Note that the menu won't show. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome, Microsoft Edge ### Operating System Windows 11
GiteaMirror added the bugbudgeting labels 2026-05-19 04:23:20 -05:00
GiteaMirror commented 2026-05-19 04:23:24 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Apr 30, 2026):

Ok. I was able to recreate this. I had to adjust my window size so that the budget table was starting to shrink down due to lack of space.

<!-- gh-comment-id:4353405856 --> @youngcw commented on GitHub (Apr 30, 2026): Ok. I was able to recreate this. I had to adjust my window size so that the budget table was starting to shrink down due to lack of space.
GiteaMirror commented 2026-05-19 04:23:25 -05:00
Author
Owner
Copy Link

@Juulz commented on GitHub (May 2, 2026):

Ok. I was able to recreate this. I had to adjust my window size so that the budget table was starting to shrink down due to lack of space.

I was able to recreate this with multiple months while working on the rightmost month.

Edit: Darn it...now I can't recreate it at all! It happened this morning though.

<!-- gh-comment-id:4364528002 --> @Juulz commented on GitHub (May 2, 2026): > Ok. I was able to recreate this. I had to adjust my window size so that the budget table was starting to shrink down due to lack of space. I was able to recreate this with multiple months while working on the rightmost month. Edit: Darn it...now I can't recreate it at all! It happened this morning though.
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 budgeting 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#80584
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?