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

Hide option for TouchID when the TouchID scanner/button isn't accessible #8105

Open
ChristopherSchultz opened this issue Jun 3, 2022 · 0 comments · May be fixed by #11410
Open

Hide option for TouchID when the TouchID scanner/button isn't accessible #8105

ChristopherSchultz opened this issue Jun 3, 2022 · 0 comments · May be fixed by #11410

Comments

@ChristopherSchultz
Copy link

On a MacBook with TouchID, the new behavior (c. 2.7) is to present an authentication dialog which contains only a "Unlock Database (TouchID)" button and a "Cancel" button. In order to use TouchID, you must click the "Unlock Database" button (or type ENTER). In order to switch to password-entry, you have to click the "Cancel" button (or type tab-enter).

Previous behavior was to immediately present the password-entry box, which was convenient as you could just start typing. Learning to press ENTER first at this point won't be too much of a problem to use TouchID.

But!

If you have the lid of your laptop closed, TouchID is not possible to use. This should be possible to detect - Apple software never prompts to use TouchID when it's closed and you are using e.g. external KVM. When the lid is closed, TouchID should no longer be the default option when pressing ENTER - it should be Cancel instead, in order to show the password-entry dialog (or, better yet, change the button to "Use Password Entry").

I say that the default should be "Use Password Entry" instead of just showing the password-entry immediately so that the muscle memory of global-hotkey-enter-authenticate still works: you just change to entering the password instead of pressing the TouchID.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants