You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @iShawnWang, can you please elobarte a bit what you have in mind? What would be the benefit compared to using requestAnimationFrame() on the main thread directly?
If I had to guess, it seems like @iShawnWang wants the ability for requestAnimationFrame() to run in inactive tabs like what you have done here for the timers. If I recall correctly, requestAnimationFrame() does not run at all in inactive tabs and will completely stop until you go back to that tab. Could be of use, but I have not needed it myself.
My take is that requestAnimationFrame() is meant to run some code right before the browser renders something on the screen. When a website is not visible it will also not render anything on the screen and therefore it seems reasonable to me that requestAnimationFrame() never gets called.
If requestAnimationFrame() is used for something that doesn't render anything but should be called periodically it should probably be replaced by setTimeout() or setInterval().
But maybe there is a use case that I just haven't thought of yet. I'd be happy to be convinced otherwise.
It is available https://developer.mozilla.org/en-US/docs/Web/API/DedicatedWorkerGlobalScope/requestAnimationFrame
The text was updated successfully, but these errors were encountered: