- From: =JeffH via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 Jul 2018 21:48:52 +0000
- To: public-webauthn@w3.org
thanks @bzbarsky, as I said, [IIUC](https://en.wiktionary.org/wiki/IIUC), which means I _might not understand correctly_, which seems to be the case here (sigh, sorry)...
Looking more closely at [credman](https://w3c.github.io/webappsec-credential-management/)'s magic [**relevant credential interface objects sub-algorithm**](https://w3c.github.io/webappsec-credential-management/#credentialrequestoptions-relevant-credential-interface-objects), i'm now thinking you & @emlun are correct, due to steps 4.2 & 4.3 in said sub-alg:
```
4. For each object in interface objects:
1. [ . . . ]
2. Let key be object’s [[type]] slot’s value. // "public-key"
3. If options[key] exists, append object to
relevant interface objects. // options[public-key] throws (?)
```
So, perhaps browser implementors can weigh-in on whether it matters if we change..
1. the [CredentialCreationOptions](https://www.w3.org/TR/webauthn/#credentialcreationoptions-extension) and [CredentialRequestOptions](https://www.w3.org/TR/webauthn/#credentialrequestoptions-extension) dictionare extensions' member name of `publicKey` to be `public-key`, or
2. the [PublicKeyCredentialType](https://www.w3.org/TR/webauthn/#credentialType)'s enumeration value to be `"publicKey"` (rather than the present `"public-key"`
..?
cc @kpaulh @agl @akshayku @jcjones @ttaubert
[publicKey]: https://w3c.github.io/webauthn/#dom-credentialcreationoptions-publickey
--
GitHub Notification of comment by equalsJeffH
Please view or discuss this issue at https://github.com/w3c/webauthn/issues/750#issuecomment-403631372 using your GitHub account
Received on Monday, 9 July 2018 21:48:58 UTC