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 https://github.com/w3c/webrtc-pc/issues/1769#issuecomment-365011992 using your GitHub accountReceived on Monday, 12 February 2018 18:16:45 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:43 UTC