[Webkit-unassigned] [Bug 63621] REGRESSION: DOMNodeRemoved doesn't fire when removing text node in contenteditable

Thu Jun 30 03:06:12 PDT 2011

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

--- Comment #3 from Erik Hesselink <hesselink at gmail.com>  2011-06-30 03:06:12 PST ---
(In reply to comment #2)
> This is a behavioral change since http://trac.webkit.org/changeset/73690, and it's intentional.  The DOMNodeRemoved is fired for the node AFTER the node is removed from the document.  However, because the node does not have a parent after the removal, it appears as if the event was never fired if you just attach an event handler on some ancestor.

I don't really understand what that changeset does exactly (an explanation would be appreciated), but the current behavior is undesirable for several reasons:

  * It violates the specification. Even though it is deprecated, this is the specification that has been implemented, and such small deviations are confusing and a recipe for bugs.
  * It is inconsistent. Most DOMNodeRemoved events still fire before removal.
  * It is hard to use. Monitoring a section of HTML (say, a contenteditable area) can now only be done by attaching event listeners to every node, which is a kind of web development antipattern.

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