-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Page Up / Down
and Home / End
keys in Auto-Type entry selector
#4530
Comments
This is likely due to differences between Linux and Windows default keyboard shortcuts. We don't register any special shortcuts for this dialog. Try using Ctrl+Up/Down for top/bottom of list on Windows. |
Confirmed not even Ctrl+Up/Down works. This will need some investigating. |
I tried several of the common keystrokes like "Shift+U/D", "Ctrl+U/D", "Alt+U/D" and "U/D" with all possible mixed modifiers. None of them were working as expected. I know there are ambivalent keystroke interpretations of all OS. But in my opinion the keystrokes for item list navigation are too overall-OS-common. |
I did try it on Debian today. It's the same OS config as used with the old version. With the mentioned old version "paging" is working fine. With the latest one it's not. Now I can say it's not OS dependent. |
Summary
In the current debian stock version
2.3.4+dfsg.1-1
it's a working feature.If I have multiple entries matching an auto type criteria and my search keyword I can use
Page Up / Down
andHome / End
to get faster to the requested database entry in the list. In the latest version2.5.3
(tested on Windows 10 only) it's not working.An example: As a software developer I'm using KeePassXC for several virtual environments provisioned with Ansible. So I have tons of database entries matching my terminal title to store the unique Ansible Vault passwords. While working with the keyboard I'm selecting the requested entry with the
Up / Down
keys which become often annoying.Desired Behavior
Please re-implement the auto type list navigation with
Page Up / Down
andHome / End
.The text was updated successfully, but these errors were encountered: