- From: Tim Cappalli via GitHub <noreply@w3.org>
- Date: Mon, 16 Mar 2026 20:49:47 +0000
- To: public-webauthn@w3.org
> Can you describe the "purpose" field from https://github.com/w3c/webauthn/issues/2360#issuecomment-3525562095. > What should be the platform behavior for this field? Instead of saying "Sign in with a passkey" for a payment or privileged action, you could optionally show "Authorize with a passkey" (as one example). > "card", "badge", "contact-card" and "contactless-card" roughly seems like the same form factor with very subtle difference. From a platform perspective - all of this seems just like a "card". I am wondering if we need all the variations? Contact-card and contactless-card are meant to be fallbacks to more specific named form factors like card and badge. Contact and contactless cards have very different experiences which could benefit from a variance in guidance for the user (e.g. tap vs insert terminology). Same with badge. "Tap your card" when expecting users to tap their employee badge may not have the expected result. -- GitHub Notification of comment by timcappalli Please view or discuss this issue at https://github.com/w3c/webauthn/issues/2360#issuecomment-4070512507 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 16 March 2026 20:49:48 UTC