Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) from Domenic Denicola on 2016-12-13 (public-webpayments-specs@w3.org from December 2016)

From: Domenic Denicola <notifications@github.com>
Date: Tue, 13 Dec 2016 12:40:24 -0800
To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
Cc: webpayments-specs <public-webpayments-specs@w3.org>, Comment <comment@noreply.github.com>
Message-ID: <w3c/browser-payment-api/issues/307/266855360@github.com>

I looked into fixing this and it's basically blocked on #346 and #338. That is, once I stringify the objects, what do we do with them? Just throw them away? Apparently they're passed on to the payment processor somehow, but that part of the spec is missing. I talked with @zkoch about what it should say roughly, so I can try a stab at it soon.

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

Received on Tuesday, 13 December 2016 20:41:38 UTC