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

[bugzilla-daemon at webkit.org]

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





--- Comment #5 from jochen at chromium.org  2012-04-02 14:17:49 PST ---
I chatted with Adam a bit, and we both agree that the test case is lame.

We considered making events that are fired asynchronously but should come before the load event could just delay the load event, but this "delay" is done between the DOMContentLoaded and the load event, so it would be still observable that the events are fired in the wrong (as in not conforming to the spec) order.

Fixing this probably requires some non-trivial changes to FrameLoader, as it triggers e.g. DOMContentLoaded (fired in Document::finishedParsing) by invoking FrameLoader::finishedParsing in FrameLoader::stopLoading and then FrameLoader continues to mess with the document and its parser.

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