Re: [w3c/browser-payment-api] Change the way we request user data (#65)

> { request: [{name: "shippingAddress"}, {name: "email",optional:true}, {name: "phone-number",optional:true}] }
> 
> seems a lot less friendly than
> 
> { requestShipping:true, requestEmail:"optional", requestPhoneNumber:"optional" }
> 
> The latter seems less complex and is more flexible.

Less complex but with no extensibility for websites to request other data types or for browsers to support these without a revision to the spec.

If it suddenly becomes very common to collect some new piece of data as part of a checkout process (like social security number or website URL) websites have to collect this as part of a separate flow until browsers catch up and start supporting them.

---
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/pull/65#issuecomment-212425304