You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When searching for a database entry in keepassxc, it is not intuitive why and which entry is set active. This default behaviour is also not yet documented in the user guide.
On inspection of the code base, I found the logic of setting an entry active here and it seems to have to do with entries being associated to a Group.
The function EntryView::setFirstEntryActive() implies that a "first" entry is set active, however I would understand, "first" as in the first entry in a entire list for instance.
Steps to Reproduce
open a populated .kdbx database with entries associated to root and child groups
search for a desired entry where multiple entries are returned as a list
observe which entry is set active visible to the user by a light green entry coloration in the GUI
Expected Behavior
The first entry in the list is set active
Actual Behavior
An entry of a child group gets selected as the one which is set active
Context
I realized this behaviour, when having a heavly populated .kdbx database and searching that somehow a child child group entry is set active where I needed to scroll down quite some time in the returned list to actually see which one it was.
Example
KeePassXC - Version 2.8.0-snapshot
Revision: 27c5c5d
Operating System: Linux
Desktop Env: Gnome/
Windowing System: X11
The text was updated successfully, but these errors were encountered:
droidmonkey
changed the title
Unexpected default behaviour of how a searched Entry is set active
First entry is not selected when a search is performed
Sep 21, 2023
Overview
When searching for a database entry in keepassxc, it is not intuitive why and which entry is set active. This default behaviour is also not yet documented in the user guide.
On inspection of the code base, I found the logic of setting an entry active here and it seems to have to do with entries being associated to a Group.
The function
EntryView::setFirstEntryActive()
implies that a "first" entry is set active, however I would understand, "first" as in the first entry in a entire list for instance.Steps to Reproduce
Expected Behavior
The first entry in the list is set active
Actual Behavior
An entry of a child group gets selected as the one which is set active
Context
I realized this behaviour, when having a heavly populated .kdbx database and searching that somehow a child child group entry is set active where I needed to scroll down quite some time in the returned list to actually see which one it was.
Example
KeePassXC - Version 2.8.0-snapshot
Revision: 27c5c5d
Operating System: Linux
Desktop Env: Gnome/
Windowing System: X11
The text was updated successfully, but these errors were encountered: