I don't understand the video conferensing use-cases. If I operate such a service and want to save battery etc, I would lower resolution and frame rate for instance to 15 fps instead of 30. I really don't want the browser to throttle me so that I loose frames which can result in a terrible user experience.
> If a site has some javascript tasks that might run long but do not directly impact UX, it's ok to run those tasks slower.
But this is a global thing so it would affect all tasks. It feels like the postTask scheduling proposal might fit this use-cases better.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/546#issuecomment-696815980