Bug 32465 - End state CSS Animation behavior is wrong and useless by definition.
Summary: End state CSS Animation behavior is wrong and useless by definition.
Status: RESOLVED DUPLICATE of bug 26869
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac OS X 10.5
: P2 Minor
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-12 00:33 PST by Gene Dronek
Modified: 2009-12-14 16:13 PST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gene Dronek 2009-12-12 00:33:49 PST 
On p25, para 2 of Safari Visual Effects Guide. 
 It says: 
.... "However unlike transitions, animations do not change property values at the end of the animation"

Yes, indeed. The properties are all reset to their beginning values.  (at the end of the animation)
You can not intervene.  The properties are reset.  period.  I presume just in case count > 1?   Grrr!

This is so brain dead.  It means one can NOT compose piecewise animation steps for
a node.     It means all animations become looped animations.  This is an insane limitation.

Who defined this behavior? 

How can you go
about piecing together count=1 animations?  Answer, you cannot.   Grrr.

Sigh.

IMHO a count=1 animation SHOULD NOT RESET at the end, but leave the properties at their final values.

Can we get the safari spec fixed?
Comment 1 Simon Fraser (smfr) 2009-12-14 16:12:18 PST 
Animation fill-modes are on our to-do list for CSS animations.

BTW, you can chain animations by using the webkitAnimationEnd event.
Comment 2 Simon Fraser (smfr) 2009-12-14 16:13:26 PST 

*** This bug has been marked as a duplicate of bug 26869 ***