W3C home > Mailing lists > Public > public-payments-wg@w3.org > May 2016

Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)

From: Tommy Thorsen <notifications@github.com>
Date: Thu, 19 May 2016 06:57:15 -0700
To: w3c/webpayments <webpayments@noreply.github.com>
Cc:
Message-ID: <w3c/webpayments/issues/130/220331895@github.com>
> No, but we should still allow apps that render HTML to do so in response to a POST and it looks like your change took that option away.

My change did indeed take that option away, as I thought that was the direction we were heading. In what situations do you think this option is useful?

If an app wants to render HTML, then it does need to use javascript to pass the response back to the user agent. If the app uses javascript to pass the response back, is it really that unreasonable to require that they use javascript to get the payment request in the first place?

---
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/webpayments/issues/130#issuecomment-220331895
Received on Thursday, 19 May 2016 13:58:08 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 19 May 2016 13:58:09 UTC