15338 2011-12-26 06:05:51 +0000 Remove the initAnimationEvent method 2012-10-02 00:24:23 +0000 1 1 1 Unclassified CSS Animations unspecified PC All RESOLVED FIXED [easy] P2 normal --- 1 dominicc dino cmarrin davve eoconnor smfr sylvaing dave.null oldest_to_newest 62027 0 dominicc 2011-12-26 06:05:51 +0000 The new pattern for programmatic event creation adopted eg by DOM4, HTML5, etc. is to define constructors for events instead of init*Event methods. For example, ProgressEvent is defined in this new style: <http://www.w3.org/TR/2011/WD-progress-events-20110809/#interface-progressevent> The AnimationEvent should have a constructor and the initAnimationEvent method should be removed. 63897 1 smfr 2012-02-08 14:06:00 +0000 *** Bug 15247 has been marked as a duplicate of this bug. *** 63898 2 smfr 2012-02-08 14:06:12 +0000 http://lists.w3.org/Archives/Public/www-style/2011Nov/0176.html 66584 3 sylvaing 2012-04-10 20:07:27 +0000 This sounds reasonable though there seeems to be interoperable support for the init*Event() methods. As such I'd like to either: a. Postpone the new pattern to the next level b. Specify both (maybe marking the init* pattern as deprecated?) 66629 4 dominicc 2012-04-12 04:13:25 +0000 (In reply to comment #3) > This sounds reasonable though there seeems to be interoperable support for the > init*Event() methods. initAnimationEvent is vendor-prefixed in Safari 5.1, not in WebKit nightly, and not implemented in Chrome. > As such I'd like to either: > a. Postpone the new pattern to the next level What does the next level mean? CSS4 Animations? > b. Specify both (maybe marking the init* pattern as deprecated?) 66667 5 sylvaing 2012-04-12 16:39:12 +0000 The method is supported by Firefox and IE10 as well as Safari. Yes, next Level -> next version of this module. (Whether that should be 4 or 2 is for another day). 66673 6 dominicc 2012-04-13 01:05:15 +0000 (In reply to comment #5) > The method is supported by Firefox and IE10 as well as Safari. It is vendor prefixed in Safari and I think it is gone in WebKit ToT. > Yes, next Level -> next version of this module. (Whether that should be 4 or 2 > is for another day). It seems odd to introduce and deprecate an API in the first version of the spec. 66674 7 sylvaing 2012-04-13 01:14:00 +0000 That's still three browsers supporting it. I don't think it's that odd for a spec to reflect the state of implementations when there already is content built around it. Though to be completely honest I can't point to content that references this specific method so it may be entirely safe to remove it. 66676 8 dominicc 2012-04-13 08:33:50 +0000 (In reply to comment #7) > Though to be completely honest I can't point to content that > references this specific method so it may be entirely safe to remove it. That was the conclusion WebKit came to when it did a clean-up of a number of init*Event methods. 75008 9 sylvaing 2012-10-02 00:24:23 +0000 Note: as suggested by Dominic, the fix follows the template of ProgressEvent. As this includes links to DOM4 ED we may have to tighten this up for LC/CR.