- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 Sep 2021 18:15:18 +0000
- To: public-webrtc-logs@w3.org
> By scheduling another task, the risk is to further delay the decision. Why are we in fear of queuing a task? Have you measured this? > This might lead to potential flakinesses or subtle interop issues. What evidence do you have of this? > My understanding is that you would like to be able to run the Microtask to select UA decision once all JS-observable microtasks have run. So far, we do not have that infrastructure and the closest to that is queue a microtask in the gym promise resolution task, not queue a task. No I want to queue a task. We queue tasks all the time, and we've shown here we can queue tasks A and B to happen in close succession. I'm not buying any issue of risk of delay. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/190#issuecomment-929506375 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 28 September 2021 18:15:19 UTC