[dom] mutation observer follow up

Is there any particular reason why the "registered observer" definition is  
sometimes referred to as "registration" and sometimes as "registered  
observer"?

What is "transient" for?

We need to add some kind of flag to "insert"/"remove" so that "replace  
all" can have a special MutationRecord object for textContent and  
innerHTML and such (and that then "insert"/"remove" not generate  
additional MutationRecord objects).

I'm not sure why there's a special algorithm for adding transient  
observers. How is it different from just appending a transient observer to  
a given node's list?

I also made various changes you should probably review (all editorial  
though, I hope!):

http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#mutation-observers
http://dvcs.w3.org/hg/domcore/


-- 
Anne van Kesteren
http://annevankesteren.nl/

Received on Friday, 17 February 2012 13:56:07 UTC