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

I think there is one more case:

* The page has asked for the payment request to be shown, but it hasn't been yet.  Suddenly things happen.  For example, the page asks for a payment request, then navigates.

As far as defining "things happen"... the problem is that it's not clear to me that the "fully active" concept captures everything.  In particular, it's not clear to me whether removing an iframe from the document means the last document that was in it is no longer "fully active", and similar for the tab closing case...

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

Received on Saturday, 18 March 2017 03:41:18 UTC