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

Re: [css3-transitions] Frame Rate

From: Simon Fraser <smfr@me.com>
Date: Tue, 25 Sep 2012 17:56:45 -0700
Cc: David Singer <singer@apple.com>, Martijn Korteweg <martijn@mediaartslab.com>, "www-style@w3.org" <www-style@w3.org>
Message-id: <15F579F1-F22F-4C88-BD01-8EC39FDF6F71@me.com>
To: François REMY <fremycompany_pub@yahoo.fr>
That seems like something that tools should do, rather than exposing it via CSS.

I don't think a frame-rate property is interesting, and would be reluctant to implement it.

Simon

On Sep 14, 2012, at 11:31 AM, François REMY <fremycompany_pub@yahoo.fr> wrote:

> I think Sylvain got it: it's to simulate low end hardware on high end hardware (ie: making sure the anim is acceptable and the jigger isn't too awful).
> 
> 
> De : David Singer
> Envoyé : 14/09/2012 19:57
> À : Martijn Korteweg
> Cc : www-style@w3.org
> Objet : Re: [css3-transitions] Frame Rate
> 
> 
> On Sep 11, 2012, at 13:31 , Martijn Korteweg <martijn@mediaartslab.com> wrote:
> 
> > Hi,
> > 
> > Every time I build css transitions into our animated experiences, our team always comes back to the same question. Can we limit the frame rate of css transition? So we can keep the feel of what our animators creating and what is shown in our html5 translated animation. I was just wondering what your thoughts are on adding a feature like this to the spec.
> > 
> > Example:
> > div {
> > transition-duration: 1s;
> > transition-property: all;
> > transition-fps: 23.976;
> > }
> 
> Given that the user-agent renders things as best it can using the available resources, why would either ask it to do worse than it can (e.g. match the monitor refresh) or ask i, implicitly, to do better than it can, and thus frustrate it?
> 
> I am sure I am missing something (especially when you quote a frame rate that is low enough to cause visible judder).
> 
> David Singer
> Multimedia and Software Standards, Apple Inc.
> 
> 
Received on Wednesday, 26 September 2012 00:57:07 GMT

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