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

Re: Mutation Observers: a replacement for DOM Mutation Events

From: Olli Pettay <Olli.Pettay@helsinki.fi>
Date: Tue, 27 Sep 2011 23:12:22 +0300
Message-ID: <4E822E26.2090603@helsinki.fi>
To: Adam Klein <adamk@chromium.org>
CC: public-webapps@w3.org, Ojan Vafai <ojan@chromium.org>, rafaelw@chromium.org, rniwa@chromium.org, Jonas Sicking <jonas@sicking.cc>, annevk@opera.com, arv@chromium.org
On 09/24/2011 12:16 AM, Adam Klein wrote:
>
> For each observer, if a registration exists which requests the
> matching mutation type and whose observed node set contains the target
> node of the mutation, a MutationRecord is appended to the observer's
> pending mutation queue. If multiple such registrations exist for a
> given observer, a single MutationRecord is delivered having the union
> of the information requested by all registrations (e.g.
> attributeOldValue).


This is actually still ambiguous.
What if attributeOldValue is first set to true for 
document.documentElement, and then false (implicitly or explicitly)
for document, should attribute values be reported?

Another problematic case is that if we have subtree A and B and both
are being observed by same observer but different options. Then some
node from A is moved to B. Which options should be used?

So, should we define that "union" means that 'true' values override
'false' values, and attributeFilter values are union'ed the usual way?

To make API somewhat more consistent, should we change
"Subsequent calls to the same MutationObserver made with the same 
|target| have the effect of resetting the options associated with the 
registration. " to follow the union-ing.

-Olli	
Received on Tuesday, 27 September 2011 20:13:10 GMT

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