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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Mar 3 21:34:15 PST 2011


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


Ryosuke Niwa <rniwa at webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mjs at apple.com




--- Comment #3 from Ryosuke Niwa <rniwa at webkit.org>  2011-03-03 21:34:15 PST ---
This isn't a bug but rather a conscious behavior change per http://trac.webkit.org/changeset/73690.  After this changeset, WebKit fires DOMNodeRemoved AFTER the node has been removed, in which case, the event doesn't bubble to the node's ancestors because by the time we fire the event, the node had already removed from the document and therefore has no parent.

You can listen to DOMSubtreeModified to detect node removal if you want to detect descendent nodes being removed.  Please let me know if this alternative isn't adequate for your purpose and poses significant challenges.

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



More information about the webkit-unassigned mailing list