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

Thu Jun 30 08:05:13 PDT 2011

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

--- Comment #4 from Ryosuke Niwa <rniwa at webkit.org>  2011-06-30 08:05:13 PST ---
(In reply to comment #3)
>   * 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.

This is a willful violation of the spec.  We've had many crashes and security vulnerabilities due to mutation events.

>   * It is inconsistent. Most DOMNodeRemoved events still fire before removal.

Right.  We'll eventually do that to doo DOMNodeRemoved.  For example, adoptNode does the same.

>   * 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.

On WebKit, you can use input event to monitor a contenteditable area. It's fired every time DOM is about to modify in the element.

Ultimately, we'd like to get rid of mutation events. See "Mutation events replacement" on public-webapps.

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