> Does that sound OK? What does that mean in practice? Do the returned promises get rejected? Remain pending forever? If they get rejected, do they trigger their callbacks? I expect this to be a significant source of non-interop especially if the payment request is triggered from an iframe that is then navigated or removed from the DOM, because browsers tend to disagree on what exactly gets torn down in those situations. :( > Specs usually don't speak about UI. Sure. This issue is about the web-observable behavior. > Whether the payment has been processed depends on when navigation or browser context destruction happened Right, this is all racy. -- 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-268333381
Received on Tuesday, 20 December 2016 19:24:27 UTC