Re: [webpayments] PROPOSAL: The PaymentRequest object SHOULD NOT expose internal state information to the developer. Any design that requires developers to manage or understand the request state is a compromise in the API design that should be avoided where possible. (#64)

> I made an argument for a different approach here: WICG/paymentrequest#42 (comment)

Right, so there are at least two mechanisms that have been identified that would address a number of the events+state+imperative issues in the Payment Request API.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/64#issuecomment-176279720