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

> Also, there is a lot of overlap with HTML's Autofill field names

There is no autofill field name for a full address. You'd either need to override the meaning of `street-address` (which technically means only the street lines, not the city, country, postal code, etc) or define a custom field name that represented the address in its entirety. I don't really like either approach - if we need to define a custom name off the bat for a key piece of information then something's gone wrong.

Another option could be to allow discrete address fields to be specified:

`formFields = ["street-address", "address-level1", "address-level2", "country", "postal-code"]`

On the one hand, I think this is less clear than what we have right now. On the other, this could be interesting in terms of validation - merchants could return incorrect or invalid form fields for the UA to display as needing correction. I quite like that.

-- 
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-262828709