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: Dave Longley <notifications@github.com>
Date: Thu, 28 Jan 2016 08:28:53 -0800
To: w3c/webpayments <webpayments@noreply.github.com>
Message-ID: <w3c/webpayments/issues/64/176264180@github.com>
> 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.

+1. I made an argument for a different approach here: https://github.com/WICG/paymentrequest/issues/42#issuecomment-173628517

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

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