W3C home > Mailing lists > Public > public-payments-wg@w3.org > January 2016

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)

From: Manu Sporny <notifications@github.com>
Date: Thu, 28 Jan 2016 08:19:35 -0800
To: w3c/webpayments <webpayments@noreply.github.com>
Message-ID: <w3c/webpayments/issues/64/176259503@github.com>
> I would assert that this requirement comes from the assumption that other features are also required like capturing shipping address data.

The counterargument to that is that you can gather data like shipping address in a declarative way - you don't need to track state and fire events to do so. I'm hesitant to add an example of how to do this to the Credentials CG specs because I don't think gathering a shipping address should be a part of the API, but if we do it declaratively, we can always switch to the "right way to do it" in the future w/o affecting Web Payments Browser API code.

Reply to this email directly or view it on GitHub:
Received on Thursday, 28 January 2016 16:20:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:13 UTC