- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 Sep 2021 21:06:54 +0000
- To: public-webrtc-logs@w3.org
> So according to browsers, >4 seconds is when a user stops associating a reaction with their action. We are talking about reducing it to 1 second as a security mitigation, probably counted in another process so we should probably reduce to half of it in the process running JS. And we want to run in slow devices, with loaded CPU and in low power mode. And browsers might want to sneak a few input events between the two tasks, especially when CPU is loaded. And the whole thing with good interoperability and predictability across all browser implementations. Let's summarise the four proposals: 1. queue a microtask: ready to spec, consistent behavior but use of await would not be possible (seen as either a pro or a con). 2. queue a task: ready to spec, but potential added delay and potential interop issues, some use of await possible (seen either as a pro or con). 3. queue a microtask that is running after the JS registered microtasks: not spec ready, consistent behavior, some use of await possible. 4. queue a task that is guaranteed to run next to the resolution task: not spec ready, would remove the potential interop issues and some of the delay from option 2. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/190#issuecomment-929625605 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 21:06:56 UTC