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 #3706] [Feedback] Context menu's #8467

New Issue
Closed
opened 2026-04-10 18:41:30 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-10 18:41:30 -05:00
Owner
Copy Link

Originally created by @UnderKoen on GitHub (Oct 21, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/3706

Right click opens an modal that allows for easy manupilaction of data clicked.

TODO:

  • Custom reports
  • Choosing an action via right-click when multiple items are selected in the budget table doesn't behave as expected (only applies to the transaction that was right-clicked)
  • Some options are missing from the right-click menu on the transactions table (Make transfer) and the shortcuts are not displayed
  • Interactions still occur when a right click menu opens (in a native menu, all interactions are normally disabled)
Originally created by @UnderKoen on GitHub (Oct 21, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/3706 Right click opens an modal that allows for easy manupilaction of data clicked. **TODO:** - [ ] Custom reports - [ ] Choosing an action via right-click when multiple items are selected in the budget table doesn't behave as expected (only applies to the transaction that was right-clicked) - [ ] Some options are missing from the right-click menu on the transactions table (Make transfer) and the shortcuts are not displayed - [ ] Interactions still occur when a right click menu opens (in a native menu, all interactions are normally disabled)
GiteaMirror added the feedbackexperimental feature labels 2026-04-10 18:41:30 -05:00
GiteaMirror commented 2026-04-10 18:41:32 -05:00
Author
Owner
Copy Link

@UnderKoen commented on GitHub (Oct 30, 2024):

@jfdoming

Interactions still occur when a right click menu opens (in a native menu, all interactions are normally disabled)

In most applications and sites the behavious is to be able to do other interactions. I personally like this more as doesn't need an extra interaction to change what you are doing.

<!-- gh-comment-id:2448286509 --> @UnderKoen commented on GitHub (Oct 30, 2024): @jfdoming > Interactions still occur when a right click menu opens (in a native menu, all interactions are normally disabled) In most applications and sites the behavious is to be able to do other interactions. I personally like this more as doesn't need an extra interaction to change what you are doing.
GiteaMirror commented 2026-04-10 18:41:32 -05:00
Author
Owner
Copy Link

@Chinoman10 commented on GitHub (Mar 6, 2025):

@jfdoming

Interactions still occur when a right click menu opens (in a native menu, all interactions are normally disabled)

In most applications and sites the behavious is to be able to do other interactions. I personally like this more as doesn't need an extra interaction to change what you are doing.

I agree with this; if the webapp doesn't have a context menu to use for that 'target', then let the system open the default one instead. Disabling the right-click context menu because you have no use for it for that particular scenario only makes the UX more frustrating (I really hate webapps that limit mouse use; I literally go out of my way and lose time just to get it running again (with local JS) out of spite).

<!-- gh-comment-id:2704288067 --> @Chinoman10 commented on GitHub (Mar 6, 2025): > [@jfdoming](https://github.com/jfdoming) > > > Interactions still occur when a right click menu opens (in a native menu, all interactions are normally disabled) > > In most applications and sites the behavious is to be able to do other interactions. I personally like this more as doesn't need an extra interaction to change what you are doing. I agree with this; if the webapp doesn't have a context menu to use for that 'target', then let the system open the default one instead. Disabling the right-click context menu because you have no use for it for that particular scenario only makes the UX more frustrating (I _**really**_ hate webapps that limit mouse use; I literally go out of my way and lose time just to get it running again (with local JS) out of spite).
GiteaMirror commented 2026-04-10 18:41:32 -05:00
Author
Owner
Copy Link

@jfdoming commented on GitHub (Mar 6, 2025):

@jfdoming

Interactions still occur when a right click menu opens (in a native menu, all interactions are normally disabled)

In most applications and sites the behavious is to be able to do other interactions. I personally like this more as doesn't need an extra interaction to change what you are doing.

I agree with this; if the webapp doesn't have a context menu to use for that 'target', then let the system open the default one instead. Disabling the right-click context menu because you have no use for it for that particular scenario only makes the UX more frustrating (I really hate webapps that limit mouse use; I literally go out of my way and lose time just to get it running again (with local JS) out of spite).

Just to be clear, the idea wasn't to disable the native context menu. It was to disable interactivity (e.g. left clicking on a button) when the custom context menu is open. We would still display native context menus

<!-- gh-comment-id:2704544428 --> @jfdoming commented on GitHub (Mar 6, 2025): > > [@jfdoming](https://github.com/jfdoming) > > > Interactions still occur when a right click menu opens (in a native menu, all interactions are normally disabled) > > > > > > In most applications and sites the behavious is to be able to do other interactions. I personally like this more as doesn't need an extra interaction to change what you are doing. > > I agree with this; if the webapp doesn't have a context menu to use for that 'target', then let the system open the default one instead. Disabling the right-click context menu because you have no use for it for that particular scenario only makes the UX more frustrating (I _**really**_ hate webapps that limit mouse use; I literally go out of my way and lose time just to get it running again (with local JS) out of spite). Just to be clear, the idea wasn't to disable the native context menu. It was to disable interactivity (e.g. left clicking on a button) when the custom context menu is open. We would still display native context menus
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 experimental feature feedback
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#8467
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?