Re: [webauthn] New PublicKeyCredential methods for JSON (de)serialization (#1703)

How do I properly respond

On Thu, Mar 10, 2022 at 9:03 AM Martin Kreichgauer ***@***.***>
wrote:

> Based on some discussion during the WG meeting today, it may be feasible
> to update the .toJSON() method here to reference
> https://webidl.spec.whatwg.org/#idl-tojson-operation, and then in plain
> language describe that the client has the responsibility to return an
> *object* with ArrayBuffer's encoded to strings using Base64URL.
>
> @kreichgauer <https://github.com/kreichgauer> Did I understand this
> correctly? Or would we still need to wrangle IDL definitions to declare
> this behavior?
>
> That's how I interpret the toJSON section of the WebIDL spec at least.
>
> I did a little digging, and Web Payments seems to want to define
> PaymentResponse.toJSON()
> <https://www.w3.org/TR/payment-request/#paymentresponse-interface>
> this way. Though they just refer to the default method steps of the
> regular operation, which we can't.
>
> The Push API is a counter example. In PushSubscription.toJSON()
> <https://www.w3.org/TR/push-api/#dom-pushsubscription-tojson> it defines
> a separate PushSubscriptionJSON dictionary. But it defines its own
> processing rules.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/webauthn/pull/1703#issuecomment-1064291832>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AYB3TUS4E4O3I47NJEN3NV3U7ITNVANCNFSM5PFXV32A>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>


-- 
GitHub Notification of comment by RyannaArline
Please view or discuss this issue at https://github.com/w3c/webauthn/pull/1703#issuecomment-1068555647 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 15 March 2022 23:18:29 UTC