W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

Re: Mutation events replacement

From: Dave Raggett <dsr@w3.org>
Date: Sat, 02 Jul 2011 19:27:11 +0100
Message-ID: <4E0F62FF.9040302@w3.org>
To: public-webapps@w3.org

> > Olli Pettay
> > Tue, 28 Jun 2011 04:32:14 -0700
> > These are *not* DOM-Event listeners. No DOM Events are created, there
> > are no capture phases or bubbling phases. Instead you register a
> > listener on the node you are interested in being notified about, and
> > will get a call after a mutation takes place.

For live concurrent editing of DOM trees, this seems to suggest that you 
are required to register an observer with *all* nodes in the DOM tree 
and not just its root node. Is that correct?  If correct, it would be a 
pain for document editing applications. For use cases like document 
editing, it would be valuable to allow observers on ancestor nodes to 
see changes to their descendant nodes.

n.b. the current mutation events work nicely for the document editing 
use cases.

  Dave Raggett<dsr@w3.org>  http://www.w3.org/People/Raggett
Received on Saturday, 2 July 2011 18:27:35 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:33 UTC