- From: <bugzilla@jessica.w3.org>
- Date: Thu, 19 Apr 2012 00:46:16 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16357 Travis Leithead [MSFT] <travil@microsoft.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #8 from Travis Leithead [MSFT] <travil@microsoft.com> 2012-04-19 00:46:14 UTC --- (In reply to comment #6) > So you'd define event constructors non-normatively along with a reference to > DOM4? Why not just point to the UI Events draft? But either way that seems > fine to me. With the latest revision of the spec, I've axed the init* methods from all of the new event interfaces that were newly defined in DOM Level 3 Events: * CustomEvent * FocusEvent * WheelEvent * KeyboardEvent * CompositionEvent ...and moved them into a non-normative appendix (now Appendix A) for historical reasons. Appendix A includes a description of the state of the world for these legacy init* methods as well as linking to DOM4 for the latest in event constructor guidance. To complete the package, I non-normatively describe the WebIDL for event constructors for the interfaces I listed previously and add: * Event * UIEvent * MouseEvent ...to ensure that all interfaces that arent deprecated (i.e., MutationEvent and MutationNameEvent) have an event constructor described. This should allow the entrepreneurial user agent to use event constructors if desired. I also make it clear that DOM L3 Events doesn't require a conforming implementation to implement the legacy init* methods or the event constructors, though an implementation should probably implement one or the other to be sure that authors can initialize these event interfaces. Appropriate deprecation notices were put on the init* methods that remain, to discourage their use, and indicate that they won't be back in a future standard. (I didn't include the notice on the Event interface since you are still describing it in DOM4.) Please let me know if this is a satisfactory resolution of this bug. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 19 April 2012 00:46:19 UTC