Re: [w3c/browser-payment-api] Add support for ShippingOption.selected. (#179)

In general, I'm a -1 to any PR that tries to collect general customer information (like shipping address, phone, email, coupons, loyalty number, etc.) via a payment request API because I think it's the wrong place to put this feature. Customer information collection should be split out into a separate spec (Customer Information API) and the group should be re-chartered to work on that API as well (doing so wouldn't slow the group down as the re-chartering process would happen in parallel). We're already doing that API, it seems. There are clean ways to mix the use of both APIs in a single UI (as the Web Payments Community Group Checkout API demonstrated).

That said, if the browser vendors (with the support of the WG) insist on pushing forward with this direction, I'm a +1 to the PR because if we're going to collect shipping address and email, we should have defaults for both of those fields.



---
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/179#issuecomment-216923737