I think this is generally fine but I'd prefer that we don't _require_ data be passed in JSON string form. In our implementation we might present the data to apps already "deserialized" so it won't look like a string to them. I think the spec ought not be so explicit in saying it will be that string form - an equivalent should also be okay. We likely to use an alternative RPC mechanism that isn't a string and this should be acceptable.
--
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/pull/382#issuecomment-267192603