Hi Paul, so this means we do not have anymore DOMnodeRemoved from the mutation events?
I find your use case sort of important specially now that I believe pages will suffer more changes based in template operations in the client. So "detecting context" is key for client apps to know where they were and what to do next. A more specific case is a 4x4 grid abcd that loses quadrant a. It is pretty important to signal the new state, let's say "null,bcd" to consumers — for example a grid rearrangement may take place. m On Thu, Oct 11, 2012 at 8:40 AM, Paul Rouget <p...@mozilla.com> wrote: > Context: in the firefox devtools, we need to track some nodes and update > different "views" based on what's happening to this node (show its parents, > show its child, show its attributes, …). > > The new Mutation observers are very helpful. But there's one thing I am not > really sure how to handle correctly . > > When a node gets detached (parent.removeChild(node)) or reparented, I need to > be notified. > > My current idea is to listen to "childList" mutations from the parent, > then, on this mutation, check if the node is still part of the children of > the parent, if not, check if it has a parent, if so, the node has been > *relocated*, then I need re-listen to a "childList" mutation from this > new parent, if no parent, the node has been *detached*. > > I was wondering if there was any better way to do that. > > Thanks, > > -- Paul > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform -- www.telasocial.com _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
