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

Re: Mutation events replacement

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Fri, 01 Jul 2011 15:13:24 -0400
Message-ID: <4E0E1C54.5060105@mit.edu>
To: David Flanagan <dflanagan@mozilla.com>
CC: public-webapps <public-webapps@w3.org>
On 7/1/11 3:05 PM, David Flanagan wrote:
> I don't think I really explained my use case on this list. See
> https://bugzilla.mozilla.org/show_bug.cgi?id=641821#c23 and
> https://bugzilla.mozilla.org/show_bug.cgi?id=641821#c25

And https://bugzilla.mozilla.org/show_bug.cgi?id=641821#c26 please....

 > Similarly, I've found it important to
> be able to distinguish between nodes that are being removed from a
> document tree and nodes that are being moved within the document tree,

Interesting, given that Gecko's DOM implementation does NOT make such a 
distinction at the moment.  Why did you find this to be important?

> Implementations will presumably maintain one list of all current
> mutations, and then will have to filter that list to deliver only those
> that match the desired type and desired subtree for which a listener is
> registered.

That's unclear.  Maintaining this list (if it were done) sounds very 
expensive; in Gecko's case we're more likely to drop on the floor the 
ones which have no registered listeners.

-Boris
Received on Friday, 1 July 2011 19:13:53 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:46 GMT