This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
(In reply to Gary Kacmarcik) >>Re: change ref to DOM3 Core. There has been no discussion of that, but if you >>feel it should be changed, please open a bug for that so that we can discuss it. and Anne comment (https://www.w3.org/Bugs/Public/show_bug.cgi?id=25359#c5) any plans for changing ref to a more current spec? I see that D3E was started a long time ago (Tom Pixley, Netscape Communications Corporation (until Jul 2002)), and now still is not a recommendation. Maybe will be better it this document would base on the current DOM spec, which at the moment has good quality (and exist in two version: W3C and WHATWG). Many other specifications for a long time refers to the latest DOM (including HTML5). This change could simplify the base D3E document, we don't need again defined basic interface, like Event, CustomEvent, EventTarget, EventListener (and probably DocumentEvent too). And some definition would be more consistent (like 'dispatch' and 'fire', which in new DOM are not synonymous). Current implementations (like browsers) when introducing new things using only the latest version of the DOM. For this implementations some concepts from D3E are still something news, but their definitions include the old DOM refs. If not changing this version of the document is worth considering such a change on the next version D3E. It's just my little thoughts, but if someone wants to write something specific (with justification) please feel free.
Yes, I feel this is long overdue now. We tried to get DOM Level 3 Events out quickly, that never happened. At this point the duplication is simply causing confusion.
<garykac> If we remove the stuff covered in DOM4, then we remove Sections 3 and 4 (and a lot of glossary items) In my opinion Section 3 is very helpful. DOM4 is economical in descriptions and has only two algorithms, but Section 3 explains everything in more detail (and other concepts, like synchronous/asynchronous, Activation triggers and behavior, etc...), has nice dispatched diagrams, just a good description for beginners (I am writing this from my own perspective and experience). Trying to understand all the basic things based only on the DOM4 (or HTML5) is difficult. Will be better just fit the text to the terminology DOM4, but not remove all. Section 4 has nice diagram for interface inheritance which is also very useful, but descriptions for basic interfaces are unnecessary (you describe everything more details, but this info in most cases can be deduced directly from the DOM algorithms). It's my small advice, both documents in some way complement each other (if we take into account the event processing).
If you feel there's something missing in http://dom.spec.whatwg.org/ you should file a bug. This part of DOM Level 3 Events is obsoleted by that and will disappear in due course.
Before make "big cleanup" please make last actual snapshot of current version for all, now last version (having its own link) derived from: W3C Working Draft 06 September 2012 http://www.w3.org/TR/2012/WD-DOM-Level-3-Events-20120906/ This will make it easier to verify which possibly important things has been removed.
We are putting together a proposed change for review. Should resolve the duplication between DOM4 and DOML3 Events.
Bulk move of all D3E bugs to the UI Events component.
Now tracking as: https://github.com/w3c/uievents/issues/19