The answer should be "abort all algorithms," IMHO. Does that sound OK? Specs usually don't speak about UI. So Chrome might chose to show a message "transaction cancelled due to navigation" in UI, but that should not be in the spec, so Firefox, for example, can do something different, if they want. Whether the payment has been processed depends on when navigation or browser context destruction happened: 1. Some payment apps complete transactions on merchant server side (Basic Card and Android Pay). If the navigation or browser context destruction happened before the PaynmentResponse is sent to the server, transaction is effectively cancelled. Otherwise, the transaction is effectively processed. 1. Other payment apps complete transactions on payment app side (PayPal and AliPay). If the navigation or browser context destruction happened before the shopping cart and payment app parameters were sent to the payment app, then the transaction is effectively cancelled. Otherwise, the transaction is effectively processed. -- 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/issues/360#issuecomment-268275837
Received on Tuesday, 20 December 2016 15:43:27 UTC