Re: [w3c/browser-payment-api] PaymentOptions seems overly verbose/overlaps with HTML (#326)

> On 1 Dec. 2016, at 11:00 am, Zach Koch <notifications@github.com> wrote:
> 
> I'm not sure I'm wild about what this means from a UX perspective. By generalizing this to a single request (e.g. requestShipping: true), we're able to create a uniform experience for users going through the shipping address flow. It also reduces the likelihood of weird things happening if a developer makes a mistake (e.g. only asking for address-level2 and not address-level1).
> 

That's kinda the point though. The developer might already have "address level 1". Ultimately, we should give developers what they request - but that's independent of the UI that is presented. 

> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or mute the thread.
> 


-- 
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/issues/326#issuecomment-264066298