- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Wed, 30 Jul 2014 17:29:07 +0200
- To: "www-dom@w3.org" <www-dom@w3.org>, "public-web-perf@w3.org" <public-web-perf@w3.org>, "www-style@w3.org" <www-style@w3.org>, Ian Hickson <ian@hixie.ch>, "public-fx@w3.org" <public-fx@w3.org>, Yehuda Katz <wycats@gmail.com>, Rafael Weinstein <rafaelw@google.com>, Adam Klein <adamk@google.com>, Adam Barth <w3c@adambarth.com>
The concept defined by "Timing control for script-based animations" https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/RequestAnimationFrame/Overview.html seems to be more widely applicable and needs to be made extensible. In particular user agents are interested in processing scroll events, media query evaluation, fullscreen state changes, orientation changes, and probably much more layout related matters in the same task. See https://www.w3.org/Bugs/Public/show_bug.cgi?id=26440 for some context. This argues that this animation frame task needs some internal queuing. Either we need buckets so scroll events are always processed before any fullscreen state changes, or we need a simple FIFO queuing mechanism on a per-task basis. Who will take ownership of this? -- http://annevankesteren.nl/
Received on Wednesday, 30 July 2014 15:29:42 UTC