- From: Khaled Zaky via GitHub <sysbot+gh@w3.org>
- Date: Mon, 28 Oct 2024 17:12:56 +0000
- To: public-webauthn@w3.org
I want to +1 this, given that we observe users often face unclear or overloaded errors, which limit their ability to troubleshoot and understand next steps. This is based on feedback we constantly receive about WebAuthn registrations. Errors like `NotAllowedError` are particularly challenging, as they obscure whether the issue is due to user cancellation, device compatibility, or other factors. Introducing more specific errors would provide users with clearer guidance and improve the experience across browsers and RPs. To support users better on our side, we reviewed common WebAuthn errors and mapped likely causes with recommended actions to help users navigate these issues effectively. Providing context-specific messages, as seen with other RPs, helps users receive actionable guidance to complete or troubleshoot registration. Having this supported in the spec would be ideal. -- GitHub Notification of comment by kzaky Please view or discuss this issue at https://github.com/w3c/webauthn/issues/2096#issuecomment-2442169666 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 28 October 2024 17:12:57 UTC