API Support for Mutation Events
Why Is This Important?
Real-time Collaboration editors
Synchroedit uses DOM mutation events in Firefox + a Comet channel to do collaborative shared editing of web documents. DOM mutation events are a great way to do this, simply capturing them, sending them to the server, then spraying them out to other web clients that subscribe to a user's edits. If IE supported this then this approach could be used for collaborative editing there.
Comment #1: Browsers might start by supporting DOM mutation events universally according to spec DOM3 Events. Of course, DOM3 Events assumed XML namespaces, but that's probably orthogonal to raising mutation events on an HTML DOM.
Comment #2: I’m not going to suggest in this list that browser vendors should fully figure out HTML tag subclassing since it may require architecture changes. Instead, point solutions like mutation events everywhere will go a long way. For example, adding onCreate, onAdd, onRemove, and onDestroy events for HTML DOM elements that developers can listen to.
Background material that request this feature
Phase I Voting - Vote for Your Top 5 Features
NOTE: PHASE I VOTING IS NOW OPEN. (2008-04-01) We have now changed the voting procedure. Instead of putting votes on each separate wiki page, we are asking people to cast their Phase I Votes on the following wiki page:
Phase II Voting
More about this later.