- From: Emil Lundberg via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Jun 2021 06:18:56 +0000
- To: public-webauthn@w3.org
Duplicate of #1362, which was closed with [this remark](https://github.com/w3c/webauthn/issues/1362#issuecomment-577405853): > On the call of 2020-01-22 it was decided that the use of ArrayBuffers is reflecting W3C direction as we understand it and that revisiting that would be too much. [...] So although I agree it's a bit cumbersome, the `encoded*` proposal will likely also be rejected with the above reasoning. However, #1362 did lead to issue #1363 and PR #1395 which added the [`getPublicKey()`](https://www.w3.org/TR/2021/REC-webauthn-2-20210408/#dom-authenticatorattestationresponse-getpublickey) method. It might be worth (re)considering if it could be worthwhile to add some methods like `PublicKeyCredential.fromJsonWithBase64Url(DOMString)` and `.toJsonWithBase64Url()`. -- GitHub Notification of comment by emlun Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1619#issuecomment-851851954 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 1 June 2021 06:19:29 UTC