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: Sat, 06 Feb 2016 07:09:26 -0800
To: w3c/webpayments <webpayments@noreply.github.com>
Message-ID: <w3c/webpayments/issues/64/180785831@github.com>
@adrianhopebailie wrote:
> Should we be defining a mechanism whereby the browser passes the execution flow control back to the website but not the user focus?

This question is part of the basis for @dlongley's Checkout API proposal here:

https://github.com/w3c/webpayments/wiki/Checkout-API

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/64#issuecomment-180785831
Received on Saturday, 6 February 2016 15:10:13 UTC

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