- From: Emil Lundberg via GitHub <sysbot+gh@w3.org>
- Date: Fri, 18 Aug 2023 11:06:14 +0000
- To: public-webauthn@w3.org
> or when they do not provide a value, the RP might prompt for it. This got me thinking - could it make sense to define an [autofill detail token](https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofill-detail-tokens) like `webauthn-authenticator-nickname` to go with this? I'm thinking perhaps that could be a way to both get the value into an input field easily and also unobtrusively offer the user to save the value to the authenticator configuration after the fact. Though I can see one complication already: in case there's not exactly one authenticator present, how does the client decide which one's nickname to autofill and optionally update? Intuitively it should of course be "the one that was just used", but that's not so easily defined when the user may wait an indefinite length of time before submitting the nickname, may have performed subsequent WebAuthn ceremonies in other tabs, etc. Perhaps you could associate by credential ID somehow, but I've a feeling this gets much too complicated for such a minor feature. -- GitHub Notification of comment by emlun Please view or discuss this issue at https://github.com/w3c/webauthn/pull/1880#issuecomment-1683752234 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 18 August 2023 11:06:16 UTC