Agree. If the only use is testing, then it should not be a feature exposed to web content.
- Maciej
On Sep 25, 2012, at 5:56 PM, Simon Fraser <smfr@me.com> wrote:
> 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.
>