Re: [w3c/payment-request] Allow incremental request of billing and shipping address (#873)

> I thought of two issues, but they seem solvable. First one is (old code + new browser) combination. If a website sets PaymentOptions.requestShippingAddress = true, a new browser needs to know how to translate that into a list. Does this mean we won't be able to leverage IDL type checking?

According to WebIDL, we should be able to distinguish between them. So if a boolean is passed, and it's `true`, then we can substitute it with some kind of default list. 

> If there's only one list, I can think of three ways: 

Oooh! I **really like** where you are going with 3!: 

 * It never over-shares if we add new address parts, 
 * it forces the developer to have good think about what they need, 
 * and it gives us a nice way to deprecate the boolean over the next few years, if we want. 



-- 
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/payment-request/pull/873#issuecomment-553312979