@ianbjacobs, great summary. Thank you. There might be a third option: * Given the set of capabilities, adding an boolean attribute or method on `PaymentRequest` that behaves the same as Apple's synchronous `canMakePayment()` - for example, `.canPay()` - could also be an option. That stops all the conflation, and let's us express the semantics of all this properly - while allowing .canMakePayment() to be handled in the service worker. -- 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-payment-apps-api/issues/96#issuecomment-278830700
Received on Friday, 10 February 2017 01:24:55 UTC