W3C home > Mailing lists > Public > www-style@w3.org > September 2012

Re: [css3-transitions] Frame Rate

From: Rik Cabanier <cabanier@gmail.com>
Date: Sat, 29 Sep 2012 09:52:44 -0700
Message-ID: <CAGN7qDBTYU76jVn-1fTqacOw-WqND=3sHyDtnPN1GdH1p8emsw@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: www-style@w3.org
Is this 60fps defined in a spec, or is it just accepted practice?

The flash player allows setting of the frame rate and this is a
*guaranteed* number
of frames per second. This means that if a script or an animation takes too
long, the animation will start skipping frames so things stay in perfect
sync (ie if you want to sync audio or video with an animation) but scripts
will still run.
The event model in browsers is not compatible with this so we'd need a
major architecture change if this should be added.

Rik

On Fri, Sep 28, 2012 at 8:06 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote:

> On 9/28/12 1:52 AM, Jon Rimmer wrote:
>
>> Let me try and illustrate it:
>>
>>     Time               0.00        0.25        0.50        0.75
>>  1.00
>> 1) Animator Drawn     x           x           x           x           x
>> 2) Tool Interpolated  x x x x x x x x x x x x x x x x x x x x x x x x x
>> 3) CSS Interpolated   xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx**xxxxxxxxxxxxxxxxxxx
>>
>
> That's actually not quite right.  That shows CSS running at 48fps.  But in
> reality it tries to do so at 60fps, which is not divisible by 24 in the
> first place.  So trying to shoehorn 24fps into this setup is a bit
> complicated.  Unless you want to run your timer at 120Hz, with the
> resulting battery hit.
>
> -Boris
>
>
Received on Saturday, 29 September 2012 16:53:12 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:00 GMT