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

From: Rouslan Solomakhin <notifications@github.com>
Date: Wed, 07 Dec 2016 09:49:34 -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/265519161@github.com>

> Has anyone from the Chrome side documented the way that the implementation follows the "spirit" of the spec and any potential mismatches?

We run the object through JSON.stringify() and propagate any exceptions.

-- 
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-265519161

Received on Wednesday, 7 December 2016 17:50:37 UTC