[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 #10 from Ojan Vafai <ojan at chromium.org>  2012-04-02 17:00:46 PST ---
(In reply to comment #9)
> (In reply to comment #8)
> > The main issue is that if you create an asynchronous event either before the DOMContentLoaded event, or between the DOMContentLoaded event and the load event (depending on which code path is executed), the said event will not be fired before DOMContentLoaded or load respectively.
> > 
> > Lacking a good test case, it's hard to describe what other browsers are doing.
> 
> How can we be talking about fixing a "bug" when we don't even know what we're testing. We need to figure out what other browsers are doing first, or else this whole discussion doesn't lead us anywhere.

That's nice in theory. In practice, browsers don't give a consistent set of APIs for determining how they behave here. All the tests that I've been able to come up with are racy and make it hard to tell definitively what a browser does.

I'm open to suggestions for how to test this better, but we should either try to match the spec or get the spec changed.

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