W3C home > Mailing lists > Public > www-dom@w3.org > April to June 2012

[Bug 16357] Avoid proliferating init*Event methods in preparation for Event constructors

From: <bugzilla@jessica.w3.org>
Date: Sat, 07 Apr 2012 00:29:04 +0000
To: www-dom@w3.org
Message-Id: <E1SGJWa-0002Wt-Il@jessica.w3.org>

Travis Leithead [MSFT] <travil@microsoft.com> changed:

           What    |Removed                     |Added
           Keywords|                            |needsReview
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #1 from Travis Leithead [MSFT] <travil@microsoft.com> 2012-04-07 00:29:03 UTC ---
For consistency, I've gone ahead and added DEPRECATION warnings for all
init*Event methods with the exception of initEvent and initCustomEvent.

Deprecation implies you don't have to implement the method unless you want to
for backwards compatibility (same definition as used for the Mutation and
MutationName events.

I didn't remove (vs. deprecate) the init* events from the newly added
interfaces because they already shipped in IE9, thus we _do_ have a need to
continue to implement them and the definition of deprecated seemed to apply
best to this scenario. But other implementations that want to claim conformance
to this spec don't need to do so, especially with event constructors.

I also left the deprecation notes somewhat vague about "some future spec"
defining them, since these particular event constructors aren't in DOM4 and
Jacob's other draft isn't yet incorporated into charter.

Let me know if this action is acceptable.

Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Saturday, 7 April 2012 00:29:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:37:00 UTC