[w3c/browser-payment-api] Response/Request semantics and cancellation (#298)

Not sure where I'm going with this (as I'm pretty new to the spec and the community), but treat this as a question and some knee-jerk reactions... 

The spec seems to have Request and Response semantics that closely mirror the fetch spec. What was the rationale for not following the conventions set forth there? 

```JS
const req = new PayRequest(method, options); 
const payResponse = await requestPayment(req); 
```

There is also some overlap between cancellable promises and this API (the .abort() method). Has thought be given about how this will interact with cancellable promises?  

Also, why is `shippingaddreesschange` and `shippingoptionschange` on the request rather than the response? 



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