UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.76 Safari/537.36

Example URL:
https://jsfiddle.net/7d06nfaf/

Steps to reproduce the problem:
Per [1], upon a call to .pause(), a media element must, among other things, queue a task to:

- Fire an event named "pause" at the element.
- Reject pending play promises with promises and an "AbortError" DOMException.

In my fiddle at [2], I call play(), pause(), play(), and pause() synchronously. I expected this to produce a sequence of interleaved pause events and promise rejections. However, instead, the promise rejections always occur (or at least log) after _all_ the event listeners have been called.

Under the assumption that the unavoidable .then() on the promises was introducing additional scheduling, I introduced a Promise.resolve() into the event listener on line 13, thinking that that would defer the logging until after the promise has been rejected. However, the events always seem to take precedence. Moreover, nesting multiple Promise.resolve()s still doesn't seem to affect the order.

I may just be misunderstanding the standard w.r.t. task queues and/or the semantics of promises here, in which case I apologize for the invalid issue, but shouldn't the promises resolve sooner?

[1] https://html.spec.whatwg.org/multipage/embedded-content.html#internal-pause-steps
[2] https://jsfiddle.net/7d06nfaf/

What is the expected behavior?
pause - reject - pause - reject

What went wrong?
pause - pause - reject - reject

Does it occur on multiple sites: No

Is it a problem with a plugin? No 

Did this work before? No 

Does this work in other browsers? N/A

Chrome version: 56.0.2924.76  Channel: stable
OS Version: 
Flash Version: Shockwave Flash 24.0 r0