Re: [w3c/browser-payment-api] Serializer behavior (#385)

You need to check what WebIDL says about serialization of nullable attributes (as it pertains to the PaymentResponse). The serialized behaviour wont be tied to the request dictionary. 

Im currently on my phone, so hard to look up. Hopefully the above helps. Let's us know tho, as I'm also interested to know what it will be 🙂

> On 21 Dec 2016, at 7:58 am, Rouslan Solomakhin <notifications@github.com> wrote:
> 
> Should PaymentResponse serializer return null, empty, or undefined payerName when requestPayerName was false in options?
> 
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub, or mute the thread.
> 


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/issues/385#issuecomment-268360020

Received on Tuesday, 20 December 2016 21:08:18 UTC