[w3c/browser-payment-api] Adding support for phone and email (#174)

This is a proposed solution for issue #1 and a counter proposal to PR
#65.

This change adds support for two new `PaymentOptions` for payer's email
and payer's phone number. These values are provided on the
`PaymentResponse` object. Since these values should not change the total
price, no `PaymentRequestUpdate` event is fired for them.

The change also adds a phone number to the `ShippingAddress` data
structure with the implication that this gets populated when
`requestShipping` is `true`.

Here are some variations to this change that should be considered:
* Do not include `requestPayerPhone` (issue #1 actually only mentions
shipping phone number)
* Do include a `requestShippingPhone` value and only populate the
`ShippingAddress.phone` value if both `requestShipping` and
`requestShippingPhone` are true.
You can view, comment on, or merge this pull request online at:

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

-- Commit Summary --

  * Adding support for phone and email

-- File Changes --

    M specs/paymentrequest.html (48)

-- Patch Links --

https://github.com/w3c/browser-payment-api/pull/174.patch
https://github.com/w3c/browser-payment-api/pull/174.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/174