- From: Ki-Eun Shin via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Aug 2023 23:51:42 +0000
- To: public-webauthn@w3.org
Kieun has just created a new issue for https://github.com/w3c/webauthn: == Inconsistent variable reference of attestation and attestationFormats in the steps == ## Proposed Change In [section 5.1.3](https://w3c.github.io/webauthn/#sctn-createCredential), the user agent instructions are defined for credential creation. In the very first step, there is a following instruction. > 3. Let pkOptions be the value of options.[publicKey](https://w3c.github.io/webauthn/#dom-credentialcreationoptions-publickey). With such instruction, the rest of instructions use `pkOptions` when referring the options.publicKey rather then using options.publicKey directly. Note that the `options` here is [CredentialCreationOptions](https://w3c.github.io/webappsec-credential-management/#dictdef-credentialcreationoptions). But, when the instructions refer `attestation` and `attestationFormats`, the spec sometimes use options.attestation and options.attestationFormats which is in fact there is no such field in the options (which is CredentialCreationOptions). Here are the some of examples in the current spec which has wrong variable usage: > 19. Let attestationFormats be a list of strings, initialized to the value of options.[attestationFormats](https://w3c.github.io/webauthn/#dom-publickeycredentialcreationoptions-attestationformats). > 20. If options.[attestation](https://w3c.github.io/webauthn/#dom-publickeycredentialcreationoptions-attestation) Similar inconsistent variable references are existed in the [section 5.1.4](https://w3c.github.io/webauthn/#sctn-getAssertion). Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1947 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 August 2023 23:51:44 UTC