[Webkit-unassigned] [Bug 82931] New: DOMContentLoaded and load events should fire asynchronously

[bugzilla-daemon at webkit.org]

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

           Summary: DOMContentLoaded and load events should fire
                    asynchronously
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Event Handling
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: jochen at chromium.org
                CC: abarth at webkit.org, ojan at chromium.org,
                    rniwa at webkit.org, tkent at chromium.org


According to http://www.whatwg.org/specs/web-apps/current-work/#the-end step 4 and step 7, the DOMContentLoaded and load events should be fired asynchronously. Currently, they're both fired synchronously.

Firefox seems to do this, all other browsers I tested (WebKit nightly, Opera 11, IE9) send the events synchronously

We could either push for an update to the spec, or send the signal asynchronously as well. The latter would allow for firing all events during DOM mutation asynchronously, without sending events that happen during DOM parsing after the load event (see e.g. issue 82778)

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