> This is implemented via a timer. What should the task queue for the timer be? This should use the same task queue as used for the "upon rejection" path. Which is currently underspecified: https://github.com/w3ctag/promises-guide/issues/52. --- There are three separate timeouts being discussed here: 1. User accepts payment request and .complete() is not called promptly 2. Shipping address/options changed and .updateWith() is not called promptly 3. updateWith(promise) is called but with a promise that does not settle promptly (already in the spec) (2) and (3) are obviously related, and are also related to https://github.com/w3c/browser-payment-api/issues/507. My proposal is that (2) doesn't need a timer, it just needs a blanket requirement that you must call updateWith() synchronously. Then the timer can be about how fast your promise settles. I will work on a PR for these. -- 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/508#issuecomment-296836861
Received on Monday, 24 April 2017 22:13:55 UTC