[DOM-Events] General thoughts on DOM-Events (Editor's Draft 20 July 2009)

I would like to bring to your consideration a concern that I've been bothered with for a longer time.

Unlike DOM-Core (and other DOM specs), the DOM-Events specification seem to be concerned to much with a web-browser/HTML, which is not what [I think] it should do. The recent modification of the event flow (introduction of the defaultView to the even propagation path) brings it even closer there and in fact tightens it fast.

However, even in that effort, the DOM-Events specification is not expected to succeed. There is already drag-and-drop, state and other modules specified separately in HTML5. There are new events in CSS3-transitions coming and more. 

So, would not it be more wise (future-proof) to take UI-related stuff away from the DOM-Events now and move it to HTML, or an other new specification? 

The DOM-Events would preserve:
1) DOM Event architecture (flow, propagation, concepts of default actions etc.)
2) Event interface and extension model, that would allow defining other interfaces in other specs
3) DocumentEvent/EventTarget/EventListener interfaces
4) MutationEvent/MutationNameEvent interfaces and events

The other specification would get the rest.

Sergey Ilinsky/

Received on Monday, 20 July 2009 11:05:59 UTC