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

[bugzilla-daemon at webkit.org]

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





--- Comment #6 from Ojan Vafai <ojan at chromium.org>  2011-03-04 00:05:09 PST ---
(In reply to comment #5)
> Strange, according to the http://www.w3.org/TR/DOM-Level-3-Events/#event-type-DOMNodeRemoved - "This event must be dispatched before the removal takes place." Is this a wrong place to look at, or we just don't care about the standards? :)

This in an intentional experiment to see if we can get away with diverging from the current specification without hurting web compatibility. If we succeed, then we will encourage other browser vendors to follow suite and will try to get the standard changed.

> I am more than happy to use a workaround using DOMSubtreeModified, but I failed to find one... Can you give me a good recipe how to use it, so that I should not miss DOMNodeRemoved events? If I remember correctly, I was not able to determine the particular DOM node that was removed from a subtree. Seems like there is no way now to catch the removed DOM node directly from the event?!

Correct. There's no way to get the list of nodes removed without keeping track of it yourself. Is there a web page that's not working? What are you trying to do that you need this information?

At a high-level, mutation events cause a lot of problems for browser developers without really helping web developers much. In addition, they have performance costs that web developers are rightfully unaware of. So we're seeing how much we can get away with modifying them to avoid these problems. There are a number of proposals for full replacements of mutation events, but none of them are currently being worked on.

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