26839 2014-09-17 22:52:17 +0000 Integrate "Timing control for script-based animations" spec into HTML 2014-11-19 21:57:09 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED P3 normal Unsorted 1 ian ian adrianba annevk contributor dbaron ian mike roc travil contributor oldest_to_newest 111724 0 ian 2014-09-17 22:52:17 +0000 See: http://lists.w3.org/Archives/Public/public-whatwg-archive/2014Sep/0046.html 111728 1 ian 2014-09-17 23:17:45 +0000 See also http://lists.w3.org/Archives/Public/public-whatwg-archive/2014Sep/0048.html 111863 2 ian 2014-09-19 23:43:04 +0000 *** Bug 26636 has been marked as a duplicate of this bug. *** 111864 3 ian 2014-09-19 23:43:16 +0000 See also http://lists.w3.org/Archives/Public/www-dom/2014JulSep/0091.html 112326 4 ian 2014-09-26 22:53:57 +0000 Looks like the model should be: 1. scroll events and other such events that we want synchronised with rendering 2. requestAnimationFrame callbacks 3. microtasks triggered by requestAnimationFrame -- beyond this point no script executes until we've painted -- 3. resolve CSS animations, transitions, etc 4. compute style 5. compute layout 6. paint 112969 5 ian 2014-10-10 18:25:16 +0000 What do people think? Is this controversial? 112970 6 travil 2014-10-10 20:13:43 +0000 I have a little trouble with the "update the rendering" concept in general--it makes a lot of assumptions about a single-threaded rendering environment. In IE's case, we use a multi-threaded rendering model, and so "update the rendering" is not going to be so straightforward. Regardless of this, if the editors of the Timing control.. spec want to integrate, then I suppose I don't object; though in general, I'm a proponent of smaller modular specs of which this plan runs counter to that goal. 112973 7 annevk 2014-10-10 22:19:13 +0000 I think this makes sense. I'd be interested in hearing how we can allow for parallelization in rendering better. Travis, I assume you still deal with synchronizing scroll events and requestAnimationFrame callbacks and such somehow? I think in the end what this is doing is synchronizing when certain rendering bits happen that have hooks in scripts. Rendering itself is after that (3-6 in Ian's list) and those things could happen in parallel. 112983 8 ian 2014-10-11 01:09:06 +0000 Travis: I'm interesting in hearing more about the multithreaded rendering model. What kinds of things do you do in separate threads? Are any of the things in comment 4 done in separate threads? 115142 9 contributor 2014-11-19 21:56:53 +0000 Checked in as WHATWG revision r8849. Check-in comment: Flesh out how rendering happens in the event loop. This also defines requestAnimationFrame() and obsoletes the 'Timing control for script-based animations' spec (by request of that spec's editors) https://html5.org/tools/web-apps-tracker?from=8848&to=8849 115143 10 ian 2014-11-19 21:57:09 +0000 Travis, let me know if the resulting spec text is problematic for IE. Thanks.