demo · v133
WebAuthn capability matrix — tailor the sign-in UI to the device
Before designing a passkey UI, sites had to try a flow and see if it errored. PublicKeyCredential.getClientCapabilities() returns a flat map of supported features — conditional UI, related origin requests, payment confirmation, hybrid transport — in one call, so the UI can hide buttons the device can't honour.
PublicKeyCredential.getClientCapabilities is not available. The table will be empty. Needs Chrome 133+.
| capability | supported | UI suggestion |
|---|
what to do with each capability
A few of the capabilities the spec defines — the Chrome 133 implementation returns these and a few more vendor-specific keys:
| key | used to enable |
|---|---|
conditionalCreate | silently upgrade a password sign-in to a passkey on the next visit |
conditionalGet | autofill-style passkey picker inside the username field |
hybridTransport | show "sign in with another device" option (QR / cloud assistance) |
relatedOrigins | share passkeys across owned domains (paypal.com ↔ paypal.me) |
passkeyPlatformAuthenticator | show OS-level "use a passkey on this device" CTA |
userVerifyingPlatformAuthenticator | require biometric/PIN on creation |
signalAllAcceptedCredentials | tell the OS to prune deleted passkeys |