[w3c/browser-payment-api] PaymentOptions seems overly verbose (#326)

What's the rationale for using booleans for the [PaymentOptions's requested members](https://w3c.github.io/browser-payment-api/#paymentoptions-dictionary)? Why not just list the things you want. 

Also, there is a lot of overlap with HTML's [Autofill field names](https://html.spec.whatwg.org/multipage/forms.html#autofill):

```JS
const options = {
  formFields: ["name"]  // why not use values from HTML spec here instead?
  // things specific to this spec would go here... like shipping
}
```

It seems less than ideal that we end up defining the same things twice in the Platform with things that are essentially meant to work together. 

@annevk @domenic, as HTML spec editors, this might be of interest to you.  

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