@domenic, you probably know best about the appropriate places to specify serializability. Here's my understanding of why the spec was written like this: Re: step 1, user agent should only JSON-stringify the data in order to pass it to the payment app. Here JSON-stringify is used as serialization for IPC. Payment apps are expected to be running in a different process, so all data destined for the payment app should be serializable. Re: step 2, JSON-parse and "convert dat to a dictionary" are equivalent, no? This should happen in the payment app process, which has received the data serialized as a string. -- 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-267145043
Received on Wednesday, 14 December 2016 20:21:26 UTC