[w3c/browser-payment-api] State how payment details modifier data is serialized and used (#404)

This closes #346, by making it clear that the data is serialized and stored in the PaymentRequest for further usage by show(), and closes #307, by finally stating all the points at which JSON-serialization happens explicitly.

A couple of points worth mentioning:

- I assumed we wanted the same swallow-all-exceptions behavior for updateWith for the JSON serialization process there.
- It's still a bit vague exactly what data is to be sent to the payment app by show(). I put in a sentence "The payment app should be sent the appropriate data from request in order to guide the user through the payment process. This includes the various attributes and internal slots of request." This is meant to convey how the data is transported. But getting this fleshed out in more detail would probably be a good idea.
You can view, comment on, or merge this pull request online at:

  https://github.com/w3c/browser-payment-api/pull/404

-- Commit Summary --

  * Editorial: rename "parsedMethodData" to "serializedMethodData"
  * State how payment details modifier data is serialized and used

-- File Changes --

    M index.html (121)

-- Patch Links --

https://github.com/w3c/browser-payment-api/pull/404.patch
https://github.com/w3c/browser-payment-api/pull/404.diff

-- 
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/404