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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Mar 4 01:31:52 PST 2011


--- Comment #12 from Ryosuke Niwa <rniwa at webkit.org>  2011-03-04 01:31:52 PST ---
I did some research on how IE9 handles this.  It fires DOMNodeRemoved (possibly others) on all the nodes it intends to remove before making any mutations.  It then mutates the DOM and fires the rest of mutation events asynchronously.

Mimicking this behavior in WebKit poses a challenge because editing code assumes that mutations happen in place (i.e. when we invoke a function).  One possible work-around is to simulate the entire editing command in some isolated world where we detect which node is removed, and then re-run the editing command on the actual DOM.  It's like run the command, undo it, and then redo it again where only the last redo part is visible to scripts.

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