- From: Diego García via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 Jun 2022 23:33:08 +0000
- To: public-webauthn@w3.org
Hi @Firstyear thanks for ur response. Yeah I read your proposal and I completely agree. Should be a consistent behavior between attestation and assertion. But what I want to know is if currently there's any workaround or something that may achieve this for registration. As I comment earlier, Google seems to achieve that on his webauthn call to navigator.credentials.create. It always show "enter your security key". I would like to know if anyone here has some kind of workaround (I don't know, maybe set some property for navigator object) for that. Hope somebody on the team make a further review on your proposal. A way to declare what auth method is been use (either a hint or a restriction) would be very helpful -- GitHub Notification of comment by justnotherdev Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1750#issuecomment-1160953045 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 20 June 2022 23:33:10 UTC