Pull request related to

#69

It seems that issue 69 is addressed by the specification, which
says to follow a credential management API algorithm. However,
since that is not what the current Chrome implementation does, I
propose to add an implementation note.

spec.bs

@@ -637,6 +637,8 @@ The [=steps to respond to a payment request=] for this payment method, for a giv
     [=Request a Credential=], passing «["{{CredentialRequestOptions/publicKey}}"
     → |publicKeyOpts|]».
 
+    Note: Chrome's initial implementation does not run the algorithm to [=Request a Credential=]. Instead, it chooses the first matching credential in the list.
+
     Note: This triggers [[webauthn-3]]'s [[webauthn-3#sctn-getAssertion|Get]] behavior
 
 1. Return |outputCredential|.