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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Apr 2 13:37:24 PDT 2012


--- Comment #4 from jochen at chromium.org  2012-04-02 13:37:20 PST ---
(In reply to comment #1)
> Can you attach the test you're using?  I'm not sure what you mean when you say we fire the load event synchronously.  Often the load event fires due to data coming in from the network, which happens asynchronously.

I read the spec as follows:

between step 1 (set the document readiness to interactive) and step 4 (fire DOMContentLoaded event), we should drop back to the message loop in any case.

If there are no scripts to be run when the documented finished parsing, we won't spin the message loop

same between steps 4 and 7

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

More information about the webkit-unassigned mailing list