You need to
before you can comment on or make changes to this bug.
According to http://www.w3.org/TR/css3-animations/#animation-events , animationstart, animationend and animationiteration events should be fired.
Created an attachment (id=158518) [details]
Simple test that reproduces the problem
From the CSS WG June 6th meeeting (http://lists.w3.org/Archives/Public/www-style/2012Jun/0105.html):
> RESOLVED: Transitions, Transforms, and Animations may be released unprefixed.
So this should be fine. I assume there's pressure to keep the prefixed versions as well?
The events are there, just prefixed, marking this a duplicate of the larger "should unprefix" -bug
*** This bug has been marked as a duplicate of bug 93136 ***
Reopening, this bug is about different issue.
Created an attachment (id=159931) [details]
This bug about animation events. In webkit, there is no way to add event listener to animated element and listen to animation events.
Jussi, you could open test file in mozilla and webkit browser and check what's the output.
(In reply to comment #6)
> This bug about animation events. In webkit, there is no way to add event listener to animated element and listen to animation events.
> Jussi, you could open test file in mozilla and webkit browser and check what's the output.
It passes in webkit if you just change the event name to "webkitAnimationStart" (note capitalization in addition to prefix).
My bad, didn't try that combination.
Thanks for clarification.