github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 03:32:54 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Feature] intelligent scroll position in Account view #1768

New Issue
Closed
opened 2026-02-28 19:54:13 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-02-28 19:54:13 -06:00
Owner
Copy Link

Originally created by @kcollett on GitHub (Jan 14, 2025).

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

If you have a large number of scheduled transactions for a particular account (or for all accounts, when going to All Accounts), when you click into an account the view is positioned at the top of the list of transactions (future/scheduled and past). If the interest is in the current part of this list (at the boundary between future and past), you might have to scroll down a bit to get there. If you click out of the account and later click back in, the view is again position at the top. The result is a lot of repeated scrolling to get to the area of interest.

Describe your ideal solution to this problem

I can think of two ways to address the problem. One is to, when entering the Account view, always position the list of transactions to make the future/past boundary visible (e.g. showing 20% future and 80% past). The second is to retain/remember the scroll position for each Account view so that the next time a given account is entered the list of transactions is positioned to where it was last positioned.

Teaching and learning

No response

Originally created by @kcollett on GitHub (Jan 14, 2025). ### Verified feature request does not already exist? - [X] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? If you have a large number of scheduled transactions for a particular account (or for all accounts, when going to All Accounts), when you click into an account the view is positioned at the top of the list of transactions (future/scheduled and past). If the interest is in the current part of this list (at the boundary between future and past), you might have to scroll down a bit to get there. If you click out of the account and later click back in, the view is again position at the top. The result is a lot of repeated scrolling to get to the area of interest. ### Describe your ideal solution to this problem I can think of two ways to address the problem. One is to, when entering the Account view, always position the list of transactions to make the future/past boundary visible (e.g. showing 20% future and 80% past). The second is to retain/remember the scroll position for each Account view so that the next time a given account is entered the list of transactions is positioned to where it was last positioned. ### Teaching and learning _No response_
GiteaMirror added the featureneeds votes labels 2026-02-28 19:54:13 -06:00
GiteaMirror commented 2026-02-28 19:54:14 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 14, 2025):

✨ Thanks for sharing your idea! ✨

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

@github-actions[bot] commented on GitHub (Jan 14, 2025): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
GiteaMirror commented 2026-02-28 19:54:14 -06:00
Author
Owner
Copy Link

@mullermn commented on GitHub (Mar 1, 2025):

I have a request #3557 which would cover this, if you want to give it an up vote!

@mullermn commented on GitHub (Mar 1, 2025): I have a request #3557 which would cover this, if you want to give it an up vote!
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 feature needs votes
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#1768
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?