W3C home > Mailing lists > Public > public-payments-wg@w3.org > February 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: Zach Koch <notifications@github.com>
Date: Fri, 05 Feb 2016 09:07:34 -0800
To: w3c/webpayments <webpayments@noreply.github.com>
Message-ID: <w3c/webpayments/issues/64/180443899@github.com>
Agreed with @adrianba here. State isn't required, either from an implementation perspective or from a web developer perspective. But it is very useful from an implementation perspective (try writing a polyfill without it). But like Adrian, I am not married to the idea.

Reply to this email directly or view it on GitHub:
Received on Friday, 5 February 2016 17:08:07 UTC

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