[w3c/browser-payment-api] Is it intended that abort() rejects the acceptPromise and resolves its return value in separate tasks? (#340)

https://w3c.github.io/browser-payment-api/#abort-method steps 8 and 9 are running async, so those two steps will queue two separate tasks to perform the actual promise manipulation.  This is observably different from performing both operations in a single task.

If this is _is_ the intended behavior, please make sure you have a test for this in the test suite, because I expect implementors will miss the subtlety here.

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