=JeffH
use case: webauthn algorithm that returns an algorithm to credential management: https://w3c.github.io/webauthn/#createCredential associated credential managment PR: https://github.com/w3c/webappsec-credential-management/pull/100
> to see whether I'm actually solving the right problem, or whether what we need is slightly different Thanks for doing this. I'll have to figure out how to play...
update 2021-11-11: this comment is now issue #1031; thus am hiding this comment as being off-topic here. ---- Original comment: Might you folks be able to point at a more...
> instead queue a task from in parallel to reject the promise but of course, doh! How does the below look? Is there an approach other than a flag-based one?...
> ... don't forget to queue a task for "resolve" too; ... Sorry, I don't understand why/how to do that, and I note you did not do such in [your...
ok, though note that anticipating a v2 augers for us to go ahead and declare the present spec as "level 1".
note that some folks are equating "silent authn" to "touchless authn"
see also #22 "Silent/touchless Authn? clarification of bit 0 in AuthenticatorData"
wrt https://github.com/w3c/webauthn/issues/199#issuecomment-247102200, see also #475
@mikewest requested: > Mind filing a bug against the credential management spec? done. See https://github.com/w3c/webappsec-credential-management/issues/87