Re: [webpayments] PROPOSAL: The PaymentRequest object MUST NOT expose internal state information to the developer. (#64)

@msporny - thanks for the updates.

I suspect that an argument against the proposal from @zkoch and @adrianba will be that the state is a requirement.

I would assert that this requirement comes from the assumption that other features are also required like capturing shipping address data.

Since, that issue is still open I would suggest we re-word this proposal to the following to have a higher chance of resolving it on the call today:

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

I would consider there to be enough evidence to support this proposal (XmlHttpRequest vs fetch).

Resolving this would be taking a step toward establishing a set of design goals for our final deliverable, which I think is valuable, without making assumptions that I think are premature.

It's your proposal so I'll leave it with you.

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