Skip to content
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

macOS: it's not possible to open entries using keyboard shortcuts #281

Open
latvia234 opened this issue Mar 8, 2023 · 3 comments
Open
Labels
bug Something isn't working macOS macOS-specific issue

Comments

@latvia234
Copy link

Description
After enabling a vault I hit cmd+f and there will appear some entries. When there are entries visible I want to open them with keyboard shortcuts. When hitting the down arrow I can select, but not open the entry.

Expected behavior
To open the entry after hitting the return-key. And after this I would like to cmd+c and cmd+v a password when needed. Why does KeePassium behave like this?

Screenshots
Screenshot 2023-03-08 at 21 18 16

@latvia234 latvia234 added the bug Something isn't working label Mar 8, 2023
@keepassium
Copy link
Owner

Hi, thanks for the feedback and sorry for the delay.

Why does KeePassium behave like this?

This behavior depends on your macOS version and which KeePassium build you run.

The native Mac version of the app is built using Mac Catalyst. There, keyboard focus/selection depends on macOS version; the app does not handle this at all and I'm not sure if this is even possible without some dirty fragile low-level tricks.

To complicate things further, it is also possible to run the iOS version of KeePassium on an Apple Silicon Mac. In this case, the system pretends to be an iPad, and handles keyboard events — you guessed it — differently again. And since this is supposed to "just work", the app has little to no control over keyboard-based selection.

I have tested this case on macOS 13.2.1, and the right panel does automatically switch to the currently selected entry.

Can you confirm your macOS version, please?

@latvia234
Copy link
Author

latvia234 commented Mar 17, 2023

sorry for the delay.

That's no problem!

Can you confirm your macOS version, please?

12.6.3

It seems that it is a better solution to just update to a newer Mac (with a newer macOS).

Edit: accidentally closed.

@latvia234 latvia234 reopened this Mar 17, 2023
@keepassium
Copy link
Owner

12.6.3

Oh, I understand you :) This was my version only a week ago. But debugging on iOS 16.4 requires Xcode 14.3, which requires macOS 13, so here we are…

It seems that it is a better solution to just update to a newer Mac (with a newer macOS).

Most likely, yeah. Though there is no guarantee this won't break again later on :)

@keepassium keepassium added the macOS macOS-specific issue label Mar 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working macOS macOS-specific issue
Projects
None yet
Development

No branches or pull requests

2 participants