W3C home > Mailing lists > Public > www-style@w3.org > August 2010

Re: [css3-transitions/animations] updates to specifications

From: Dean Jackson <dino@apple.com>
Date: Tue, 24 Aug 2010 04:39:36 +1000
Cc: www-style@w3.org
Message-Id: <66638A0F-8A4F-4131-9E41-60857569B071@apple.com>
To: Tab Atkins Jr. <jackalmage@gmail.com>

On 23/08/2010, at 4:05 PM, Tab Atkins Jr. wrote:

> On Sun, Aug 22, 2010 at 5:16 PM, Dean Jackson <dino@apple.com> wrote:
>> I've updated the CSS3 Transitions and Animations editor's drafts with the following changes (as agreed on at the last CSS f2f meeting):
>> 
>> CSS 3 Transitions - http://dev.w3.org/csswg/css3-transitions/
>> 
>> - A new timing-function that allows discrete changes, called "steps". It breaks the domain of the animation into a number of equal intervals, each the same increment over the output percentage. The output value is flat along an interval. You control the number of intervals and whether or not the change in output value happens at the start or the end. There are some shorthands, step-start and step-end, which provide the common case - a single discrete change in output.
>> 
>> CSS 3 Animations - http://dev.w3.org/csswg/css3-animations/
>> 
>> - Incorporate the new timing function above
>> 
>> - A new property animation-fill-mode that allows the effects of an animation to extend before it begins (between the time the animation is applied and the starting delay) and after its duration completes (until the animation is removed). This is an extremely helpful property for authors, who otherwise would have had to set the property values for the beginning and end of animations via script.
> 
> Sounds good!

There was a resolution the CSSWG made that still need to be included in the specification:

- Text about all properties being transitionable/animatable, even if they are discrete values

>> FYI: animation-fill-mode has been implemented with the -webkit- prefix in WebKit for a few months now. It shipped in Safari 5 and iOS 4.
> 
> And it is at least registered as a valid value in current Chrome,
> though I haven't yet seen if it actually works.

Neither have I, but I assume it would work - AFAIK, with the exception of the additional hardware acceleration path that Safari can use, both browsers share the same animation engine.

BTW - user feedback on this new property has been overwhelmingly positive.

Dean
Received on Monday, 23 August 2010 18:40:14 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:30 GMT