Have you searched for an existing feature request?
Brief Summary
This feature makes it possible for passkeys to appear in the autofill drop-down menu.
Without it, signing in with passkeys can be slower, or even impossible (see PayPal's example below).
From the article: KeePassXC Passkeys: Analysis of Sign-Ups and Logins
URL: https://www.corbado.com/blog/keepassxc-passkeys
Conditional UI gap: KeePassXC lacks Conditional UI support, preventing usernameless login and requiring more clicks than competitors like 1Password or Dashlane.
and a little lower:
Lack of Conditional UI: KeePassXC misses out on one of the key benefits of passkey technology - seamless, usernameless login. Other password managers have done better here, minimizing the number of clicks the user needs to do to log in.
Another article about Conditional UI I just found: https://www.corbado.com/blog/webauthn-conditional-ui-passkeys-autofill
Example
Example 1: Google
Before switching to KeePassXC, I was using Bitwarden. When I signed in to Google, the passkey appeared in the autofill drop-down menu, and I could simply click it to log in.
With KeePassXC, I first have to enter my username, then select the passkey option, and finally click the KeePassXC pop-up window. It's much slower.
Example 2: PayPal
If I understand correctly, PayPal only supports the autofill flow. So even though I was able to create the passkey successfully, it's impossible to use it to log in.
Context
No response
Have you searched for an existing feature request?
Brief Summary
This feature makes it possible for passkeys to appear in the autofill drop-down menu.
Without it, signing in with passkeys can be slower, or even impossible (see PayPal's example below).
From the article: KeePassXC Passkeys: Analysis of Sign-Ups and Logins
URL: https://www.corbado.com/blog/keepassxc-passkeys
Conditional UI gap: KeePassXC lacks Conditional UI support, preventing usernameless login and requiring more clicks than competitors like 1Password or Dashlane.
and a little lower:
Lack of Conditional UI: KeePassXC misses out on one of the key benefits of passkey technology - seamless, usernameless login. Other password managers have done better here, minimizing the number of clicks the user needs to do to log in.
Another article about Conditional UI I just found: https://www.corbado.com/blog/webauthn-conditional-ui-passkeys-autofill
Example
Example 1: Google
Before switching to KeePassXC, I was using Bitwarden. When I signed in to Google, the passkey appeared in the autofill drop-down menu, and I could simply click it to log in.
With KeePassXC, I first have to enter my username, then select the passkey option, and finally click the KeePassXC pop-up window. It's much slower.
Example 2: PayPal
If I understand correctly, PayPal only supports the autofill flow. So even though I was able to create the passkey successfully, it's impossible to use it to log in.
Context
No response