- From: James Robinson <jamesr@chromium.org>
- Date: Wed, 17 Sep 2014 15:44:16 -0700
- To: whatwg <whatwg@lists.whatwg.org>, Cameron McCormack <cam@mcc.id.au>
Cameron and I are editors of the "Timing control for script-based animations" spec, more commonly known as the spec for requestAnimationFrame. This spec has some outstanding feedback from folks like Anne that needs to be addressed at a basic editorial level that I haven't had bandwidth to address. It also needs to integrate more tightly into the HTML's rendering model to get proper timing. I think that adding the appropriate hooks to both specs will be complicated and I know I don't have the bandwidth to do this correctly, so I propose that we simply move this algorithm into HTML itself and ask that the HTML editors (aka Hixie) take over this part of the spec. If this doesn't happen, I'm afraid that the spec will languish and it'll be hard to correctly specify the various things that are supposed to coordinate with each other to produce a smoothly functioning and consistent system. Specifically, the spec defines the following WebIDL: partial interface Window { long requestAnimationFrame(FrameRequestCallback callback); void cancelAnimationFrame(long handle); }; callback FrameRequestCallback = void (DOMHighResTimeStamp time); and a relatively simple processing model that should integrate tightly into HTML 8.4.1.2 "Processing Model"'s "Update the rendering" step: https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/RequestAnimationFrame/Overview.html#processingmodel I'm happy to provide any help with technical issues here, but can't promise to actually edit anything useful. Does this sound useful to folks? - James
Received on Wednesday, 17 September 2014 22:44:57 UTC