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

It turns out much of this is unnecessary as per the event loop spec tasks on non-fully active documents are not executed. So now that we are properly queuing tasks to do observable things, (B) and (C) from https://github.com/w3c/payment-request/issues/360#issuecomment-274213058 are not a concern.

(A) is still a potential concern though, so I will fix it. Also, in that comment I said we'd just leave the promise pending, but now I think just rejecting with an "AbortError" DOMException makes more sense.

-- 
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/payment-request/issues/360#issuecomment-321411150

Received on Wednesday, 9 August 2017 23:44:23 UTC