- From: ianbjacobs <notifications@github.com>
- Date: Tue, 19 Jul 2016 06:53:16 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
Received on Tuesday, 19 July 2016 13:54:11 UTC
@adrianhopebailie wrote: "I disagree, the requirements here will impact what is passed in the request (and this PR is for a change to the PaymentRequest API)" Right now the payment apps api spec is defined in terms of conformance for user agents. User agents are going to have to change their behavior to implement the spec, including their implementation of the payment request api. For instance, they will need to "hand off control" at a particular place in the payment request API algorithm, then receive it again. Therefore, I think it's ok to define all payment app-related behavior in the payment app spec, and this COULD involve changes to payment request API. Ian --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/browser-payment-api/pull/223#issuecomment-233639626
Received on Tuesday, 19 July 2016 13:54:11 UTC