Have you searched for an existing feature request?
Brief Summary
I hope this is okay to raise as a sub-issue of #12921 in light of #12921 (comment) but please feel free to close if a different solution has already been considered.
What I noticed
When a browser extension triggers a passkey registration, the Passkey Import dialog shows a Group drop-down that lists every group in the database as a flat slash-separated path, e.g. Root, Root/Open source, Root/Open Source/GitHub etc.
Steps to reproduce
- Open a database with several nested groups.
- From a browser with the KeePassXC extension, register a new passkey on any site (e.g. GitHub → Settings → Passkeys → Add).
- In the KeePassXC Passkey Import dialog, open the Group drop-down.
- Observe a flat list of path strings
Example
Claude noticed that Database → Database Settings → Secret Service integration already uses a QTreeView backed by GroupModel for the same kind of group selection. I was wondering whether that same pattern might also be suitable here, to show the hierarchy as a collapsible tree. I could be wrong about whether the two contexts are comparable, though; the Secret Service setting is a one-time config choice, whereas the passkey dialog is used during a live registration flow.
I've drafted a patch if it would be useful to look at. The result looks like this:
Context
For databases with many groups, the picklist can be a bit unwieldy to scroll through, and I wasn't sure if that was the intended experience.
Have you searched for an existing feature request?
Brief Summary
I hope this is okay to raise as a sub-issue of #12921 in light of #12921 (comment) but please feel free to close if a different solution has already been considered.
What I noticed
When a browser extension triggers a passkey registration, the Passkey Import dialog shows a Group drop-down that lists every group in the database as a flat slash-separated path, e.g.
Root,Root/Open source,Root/Open Source/GitHubetc.Steps to reproduce
Example
Claude noticed that Database → Database Settings → Secret Service integration already uses a
QTreeViewbacked byGroupModelfor the same kind of group selection. I was wondering whether that same pattern might also be suitable here, to show the hierarchy as a collapsible tree. I could be wrong about whether the two contexts are comparable, though; the Secret Service setting is a one-time config choice, whereas the passkey dialog is used during a live registration flow.I've drafted a patch if it would be useful to look at. The result looks like this:
Context
For databases with many groups, the picklist can be a bit unwieldy to scroll through, and I wasn't sure if that was the intended experience.