Re: [webrtc-pc] Semi-sync replaceTrack API pre-initial-negotiation is bizarre.

Even if a promise is immediately resolved/rejected its then() executes asynchronously in the next task. I think a "sometimes partially synchronous" API with promise is unexpected and confusing. +1 to always queuing a task for observable effects.

GitHub Notification of comment by henbos
Please view or discuss this issue at using your GitHub account

Received on Monday, 12 February 2018 18:16:45 UTC