- From: Jenan Wise <notifications@github.com>
- Date: Fri, 06 Oct 2017 15:29:55 +0000 (UTC)
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 6 October 2017 15:30:20 UTC
@rsolomakhin Ah, fascinating! Thanks for detailed response and Chrome details! That sounds like a great workaround, but it sort of falls out of some assumptions about the API rather than specific contracts, right? 1. Right now, it looks like the Payment Handler spec [says](https://www.w3.org/TR/payment-handler/#the-paymentrequestevent) that handlers receive `total` (although it's not clear to me how `canMakePayment` events differ from these -- am I looking in the wrong place?) 2. The spec is rather light on `canMakePayment()` implementation details. There doesn't seem to be anything stopping a browser from forcing `canMakePayment()` being called before `show()`, right? -- 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/payment-request/issues/639#issuecomment-334788861
Received on Friday, 6 October 2017 15:30:20 UTC