[Webkit-unassigned] [Bug 63242] New: DOM mutation events (DOMNodeInserted and DOMNodeRemoved) have incorrect relatedNode during editing actions

[bugzilla-daemon at webkit.org]

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

           Summary: DOM mutation events (DOMNodeInserted and
                    DOMNodeRemoved) have incorrect relatedNode during
                    editing actions
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Macintosh Intel
        OS/Version: Mac OS X 10.6
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: HTML DOM
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: hesselink at gmail.com


Created an attachment (id=98332)
 --> (https://bugs.webkit.org/attachment.cgi?id=98332&action=review)
Testcase showing the bug

In recent nightlies of Webkit (Version 5.0.5 (6533.21.1, r89368)) as well as the current version of Chrome, the DOMNodeInserted and DOMNodeRemoved events have an incorrect 'relatedNode' property. According to the spec, this should be the parent node of the inserted or removed node, but this is no longer the case during editing actions in a 'contenteditable' element.

I've attached a test case. It contains a contenteditable div, and attached event listeners to it for DOMNodeInserted and DOMNodeRemoved. It then logs all these events to the console, also indicating if the relatedNode is the parent node. You can reproduce the bug by putting the cursor inside the bold 'bar' and pressing enter.

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