[Webkit-unassigned] [Bug 55666] DOMNodeRemoved events are not dispatched

Fri Mar 4 00:29:31 PST 2011

https://bugs.webkit.org/show_bug.cgi?id=55666

--- Comment #9 from Ryosuke Niwa <rniwa at webkit.org>  2011-03-04 00:29:31 PST ---
(In reply to comment #8)
> I already use the DOMSubtreeModified event to hack around the "missing" DOMNodeRemoved events, but in some corner cases it still does not work. I do not want to traverse the whole subtree every time a node is removed for obvious performance reasons.

Why do you need to detect a node removal?

>Also it may not be a good idea to listen for DOMNodeRemoved on every DOM node inside the subtree - it does not seem to be a robust solution, and, if I understand correctly, the parent node of the remove node will still be unavailable.

Yes, the parent node won't available.

> In other words, a DOMNodeRemoved event dispatched BEFORE the removal takes place - is exactly what I need. And now I have to invent a workaround to "emulate" it :)

For what do you use DOMNodeRemoved?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.