Category selection is inconsistent #14

Closed
opened 2026-02-28 18:45:37 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @Deguello on GitHub (Nov 18, 2021).

I haven't made a complete list, though I probably should, but in some places in the (Mac) app, a category can be selected by partially typing the name and hitting TAB once there's only one option and other places require ENTER to make the selection.

IMO, TAB is preferable but consistency is even more preferable.

Originally created by @Deguello on GitHub (Nov 18, 2021). I haven't made a complete list, though I probably should, but in some places in the (Mac) app, a category can be selected by partially typing the name and hitting TAB once there's only one option and other places require ENTER to make the selection. IMO, TAB is preferable but consistency is even more preferable.
GiteaMirror added the user interface label 2026-02-28 18:45:37 -06:00
Author
Owner

@jlongster commented on GitHub (Dec 6, 2021):

Yeah, this definitely needs some UX work. I have some concern with tab where it's easy to accidentally select something when you didn't mean to. However I think you're right; tab is the way to go and if you want to tab away without saving you do "escape" first and then tab.

@jlongster commented on GitHub (Dec 6, 2021): Yeah, this definitely needs some UX work. I have some concern with tab where it's easy to accidentally select something when you didn't mean to. However I think you're right; tab is the way to go and if you want to tab away without saving you do "escape" first and then tab.
Author
Owner

@MatissJanis commented on GitHub (Mar 30, 2023):

👋 We're slowly moving things over to the new autocomplete component. That should address some of the usability issues. So I'll close this one off for now so people don't accidentally pick it up and start implementing yet another autocomplete component :)

Tracking here: https://github.com/actualbudget/actual/issues/773

@MatissJanis commented on GitHub (Mar 30, 2023): :wave: We're slowly moving things over to the new autocomplete component. That should address _some_ of the usability issues. So I'll close this one off for now so people don't accidentally pick it up and start implementing yet another autocomplete component :) Tracking here: https://github.com/actualbudget/actual/issues/773
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#14