- From: <bugzilla@jessica.w3.org>
- Date: Fri, 09 Mar 2012 00:50:57 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14051 Travis Leithead [MSFT] <travil@microsoft.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #5 from Travis Leithead [MSFT] <travil@microsoft.com> 2012-03-09 00:50:55 UTC --- I'd love to see these constructors defined as well. I did a quick check of DOM4, and didn't see definitions for the derived events that we have bugs on: 14050, 14051, 14052, 14053, 14054, 14055. This is an interesting situation. I like event constructors, don't get me wrong, but they are a "new" feature introduced by DOM4 (which has the algorithm that describes how they work for the Event interface as well as any derived interfaces, according to 4.4 Constructing events (http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#constructing-events). I'd prefer not to add them to DOM3 at this time. Anne, DOM4 seems to provide the right hook to allow any derived Event interface that has a constructor to be specified. Do you think we need any follow-up action to account for UIEvent, MouseEvent, KeyboardEvent, TextEvent, CompositionEvent constructors? For example, it might be nice to note which of the "common" events have constructors? -- 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 Friday, 9 March 2012 00:50:59 UTC