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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Apr 2 15:08:10 PDT 2012


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


Ryosuke Niwa <rniwa at webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ap at webkit.org




--- Comment #7 from Ryosuke Niwa <rniwa at webkit.org>  2012-04-02 15:08:09 PST ---
(In reply to comment #0)
> 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

I'm not certain if we want to change our behavior then.

It seems like there's some confusion here due to the bad test case. Could someone summarize the current state of this bug? (e.g. what's wrong with our current behavior, other browsers' behaviors, and possible solutions).

-- 
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