[w3c/browser-payment-api] Need to define the interaction of payment API with navigation and browsing context destruction (#360)

I don't see anything in the spec that describes what happens if any of the following happen while a payment request is in progress:

1. Navigation to a different happens in the browsing context which contains the document/window that the payment request was created in.
2. Navigation happens in some ancestor browsing context.
3. The browsing context which contains the document/window the payment request was created in is torn down (e.g. iframe removed from the DOM).
4. Some ancestor browsing context is torn down (e.g. tab which contains an iframe that made a payment request is closed).

Part of the issue here, of course, is that there is a bit of a lack of spec clarity around what happens to event listeners and Promises when these things happen.  But even apart from that, it's not clear what should happen to the UA-provided payments UI when these things happen.  It's also not clear what happens if these things happen between the user dismissing the browser-provided UI (e.g. accepting the payment) and the "user accepts the payment request algorithm" running.

-- 
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