-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make load event comply with the spec #1416
Comments
|
|
@jdm is there a set of web platform tests that test these features? :-) |
Unfortunately the ones that might be applicable seem to involve other unfinished features such as Element.style and inline event handlers (body.onload = ...). We'll probably want to write some simple ones ourselves. |
This is heavily tied to #1879 (document lifecycle, incl. new HTML parser) |
To some degree - I think we can create a separate DocumentLoader object that acts as an interface to the resource task and can be used by the parser and DOM objects. |
I did this. |
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-end.html#the-end
We need the ability to track resource loads that are fired during the initial parse. It likely makes sense to do this in concert with the BrowserContext implementation (#1417).
The text was updated successfully, but these errors were encountered: