Re: [webrtc-pc] setRemoteDescription and ontrack order of events: SRD before ontrack?

Actually, I found that "addstream" is fired _after_ the promise's then-callback is invoked in Chrome for the exact same reasons as "track" in the spec and in my work-in-progress: it's queued to fire in the next loop.

A `[[pendingTrackEvents]]` would be a nice solution to this if we want a promise to be resolved after all events have guaranteed to be fired, since a fired track event does not tell you how many more events are pending.

-- 
GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1508#issuecomment-318022206 using your GitHub account

Received on Wednesday, 26 July 2017 11:06:16 UTC