28644 2015-05-15 14:02:05 +0000 Add an optional parameter to requestAnimationFrame to indicate when the callback should be called 2019-03-29 19:13:52 +0000 1 1 1 Unclassified WHATWG HTML unspecified PC All RESOLVED MOVED P2 normal Unsorted 1 bugs ian annevk d igrigorik mike ojan rbyers contributor oldest_to_newest 120320 0 bugs 2015-05-15 14:02:05 +0000 I've seen rather often in various tests that one wants to actually get a callback called right after the normal animation frame stuff, usually even async. So something like requestAnimationFrame(function(now) {}, { async: true }); might work pretty well. Not sure what the /now/ passed to the callback should be in that case. I guess it shouldn't be the /now/ defined in https://html.spec.whatwg.org/multipage/webappapis.html#processing-model-9:run-the-animation-frame-callbacks, but the value should be updated just before calling such async callbacks. 123492 1 annevk 2015-10-06 06:53:16 +0000 Do you mean this would be invoked as part of a new substep 11 of the overall rendering update step? In that case { postRendering: true } might be more appropriate. Rick, Ilya, any thoughts on this? 123524 2 bugs 2015-10-06 16:47:33 +0000 Either step 11 could call them or step 9 would have a substep to take the current "late-callbacks" and queue a task to call them. 123526 3 igrigorik 2015-10-06 16:53:59 +0000 Isn't requestIdleCallback already filling in this gap, and in a better and more flexible way? See: https://w3c.github.io/requestidlecallback/ p.s. available in Chrome Canary and shipping in M48. 123529 4 bugs 2015-10-06 17:16:06 +0000 This has very little to do with requestIdleCallback. The issue is that we currently put too much pressure to animation frame tick time, yet there are things which could run right after the tick. 123530 5 rbyers 2015-10-06 17:20:45 +0000 How does this relate to setImmediate (https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/setImmediate/Overview.html)? I don't fully understand the use cases here, /cc ojan@ who is probably a better blink contact. 124694 6 d 2016-01-24 05:45:21 +0000 (In reply to Rick Byers from comment #5) > How does this relate to setImmediate > (https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/setImmediate/Overview. > html)? setImmediate is unaware of the animation lifecycle and just queues a task as soon as possible (but on the task queue, so it might happen after other tasks, input, even rendering if you manage to catch it on the 16 ms boundary). So, also pretty unrelated. 128781 7 annevk 2017-07-24 13:26:54 +0000 Olli, is this still something you want? 128782 8 bugs 2017-07-24 15:06:49 +0000 I'm pretty sure yes. I've seen this often at least in tests doing something like requestAnimationFrame(function() { setTimeout(function() { /* do something*/}); }) 128783 9 annevk 2017-07-24 15:09:59 +0000 But there's no guarantee there's no other animation frame in between in that case, right? If there's already some tasks queued, you won't run directly after the frame. 128784 10 bugs 2017-07-24 15:18:23 +0000 Sure. I don't have strong opinion whether it should be right after next tick, or async task after next tick. 129647 11 d 2019-03-29 19:13:52 +0000 https://github.com/szager-chromium/requestPostAnimationFrame