https://bugs.kde.org/show_bug.cgi?id=518437
Bug ID: 518437
Summary: When matching, deleting or otherwise disappearing a
transaction, focus should be on next transaction on
the list
Classification: Applications
Product: kmymoney
Version First 5.2.2
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: ux-ui
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
I believe this is how it used to work, but I might be misremembering things.
When matching, deleting or otherwise making a transaction entry disappear,
focus should be placed on next transaction on the list, not the last (newest)
overall in ledger. This is a substantial UX obstacle when working with the
ledger, as it requires constant rewinding of the ledger to a previous location
*and* a it imposes a substantial cognitive effort to actually locate that
position you were just at.
STEPS TO REPRODUCE
1. Delete a transaction somewhere in the middle of the list of transactions
OBSERVED RESULT
Ledger is scrolled to the bottom-most (newest) transaction.
EXPECTED RESULT
After causing a transaction disappear, ledger position should Ideally not move
at all. Focus should placed on next transaction in relation to the
"disappeared" transaction, or the previous one, if the "disappeared"
transaction was the last one shown in the ledger's viewport.
--
You are receiving this mail because:
You are watching all bug changes.
