Code Search indicates that nobody uses this. Now that WebKitAnimationEvent has a constructor, we should remove this method.
Created attachment 113878 [details] Patch
Comment on attachment 113878 [details] Patch Are there already tests for the constructor version?
(In reply to comment #2) > (From update of attachment 113878 [details]) > Are there already tests for the constructor version? Yes, in fast/events/constructors/webkit-animation-event-constructor.html. Should I note that in the ChangeLog?
(In reply to comment #3) > (In reply to comment #2) > > (From update of attachment 113878 [details] [details]) > > Are there already tests for the constructor version? > > Yes, in fast/events/constructors/webkit-animation-event-constructor.html. Should I note that in the ChangeLog? No, that's fine. I just wanted to be sure we weren't losing test coverage.
Comment on attachment 113878 [details] Patch Don’t want to commit this yet until I confirm the CSS3 Animations spec deprecates initAnimationEvent.
Comment on attachment 113878 [details] Patch Remove this from CQ for now. I filed <https://www.w3.org/Bugs/Public/show_bug.cgi?id=15338> to change the CSS Animations spec to remove this method.
I don't think you need to wait for the spec to be updated here. The platform as a whole is clearly moving in this direction, so it seems very unlikely to me that this spec won't be updated eventually to match. The longer this stays in trunk, the more likely we'll get stuck unable to remove it due to compatibility concerns. Filing the spec bug is important of course.
Committed r103751: <http://trac.webkit.org/changeset/103751>