- From: Zhirui Zhang via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Jun 2024 12:44:27 +0000
- To: public-webauthn@w3.org
> ## `NoCredentialsError` and `UserCancelledError` > We independently came up with the same two `NoCredentialsError` and `UserCancelledError` errors that @AdamEisfeld has already proposed, so I'm in support of these. > > For `NoCredentialsError`, we agree that if the user cancels out of the browser's "you have no credentials for this site" it necessarily means they tried to auth. That should count as consent, so why not let that propagate through to the RP? > > For `UserCancelledError`, it would be great to pull this out of `NotAllowedError` as a new default error that gets returned **after the user specifically cancels out** of the modal experience. `NotAllowedError` is currently so overloaded it's difficult to understand whether the user experienced a legitimate issue with their browser + OS + authenticator, or simply decided to cancel out. @MasterKale Sorry to interrupt, but what's the plan about adding these errors? I'm a new developer and dealing with lots of `NotAllowedError` currently. `UserCancelledError` or `TimeoutError` is exactly what I need. What other measures can I take to solve this problem temporarily since new releases will take a while. -- GitHub Notification of comment by Zhirui-Zhang Please view or discuss this issue at https://github.com/w3c/webauthn/issues/2062#issuecomment-2178614634 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 19 June 2024 12:44:28 UTC