[Webkit-unassigned] [Bug 46936] New: Make DOM Mutation Events Asynchronous

[bugzilla-daemon at webkit.org]

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

           Summary: Make DOM Mutation Events Asynchronous
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: P2
         Component: HTML DOM
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: rniwa at webkit.org
                CC: eric at webkit.org, mjs at apple.com, darin at apple.com,
                    justin.garcia at apple.com, fishd at chromium.org,
                    jparent at google.com, ojan at chromium.org,
                    aa at chromium.org, arv at chromium.org, enrica at apple.com


DOM mutation events are sources of many security holes and crashes in HTML editing.  I propose to make them asynchronous and in particular delay all mutation events triggered by mutations inside a EditCommand until the completion of the command to eliminate the chance of JavaScript modifying DOM in a way editing code does not expect.  There are two benefits to this approach:
* Robust Security - Many crashes in HTML editing will be eliminated
* Performance Gain - Multiple mutation events can be collapsed into one if parent nodes of the subtree being modified are same

While there is a fear that this might break the existing websites, I recently discovered that Microsoft Internet Explorer 9 Beta fires DOM mutation events asynchronously.  Given the market share of the Internet Explorer, it seems clear to me that popular websites will eventually (if not immediately) support asynchronous DOM mutation events.

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