- From: Nina Satragno via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Oct 2023 19:09:05 +0000
- To: public-webauthn@w3.org
If we put only the option on `AddCredential`, then how would you test your website's behaviour on credential creation? Here's a proposal: * Have `backup-eligibility` and `default-backup-state` be a setting on `AddVirtualAuthenticator`. This lets you test what happens for various values when creating a credential. * Add `backup-eligibility` and `backup-state` to `AddCredential`, which lets you test assertions. * Add a `Set Backup State` method to avoid having to recreate a credential. I'm not a fan of the remove-and-add proposal because if we add more state to the credentials, then the developer has to make sure they update all the places where they do this if they want to get the exact same credential when they update their e2e testing browser. Or worse: if your webdriver version drifts from your browser version, it might be impossible to recreate the same credential, since the old webdrive might not know about new state. -- GitHub Notification of comment by nsatragno Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1987#issuecomment-1779888074 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 25 October 2023 19:09:08 UTC