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: Manu Sporny <notifications@github.com>
Date: Tue, 09 Feb 2016 19:41:15 -0800
To: w3c/webpayments <webpayments@noreply.github.com>
Message-ID: <w3c/webpayments/issues/64/182184065@github.com>
> I'm for removing the line readonly attribute PaymentRequestState state; from the PaymentRequest interface WebIDL. I haven't seen any good uses for this variable.

Great, thanks @rsolomakhin - we can always add it back in if we find a good use for it. This addresses my concern w/ the Microsoft/Google proposal wrt. state. Happy to close the issue at this point. 

@adrianhopebailie do you want to close this now, or resolve the proposal on the call and record it as a RESOLUTION?

Reply to this email directly or view it on GitHub:
Received on Wednesday, 10 February 2016 03:41:42 UTC

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