1

This has not been answered here or there. These questions are poorly worded, and the answers are all along the lines of "use DOMReady".

I want to ensure that code is run only if the page has finished loading. I cannot alter the HTML file itself, but if I could, I would do something that amounts to this:

<!DOCTYPE html>
<html>
  <head>
    <script>window.loaded=false;</script>
  </head>
  <body onload="window.loaded=true;">
    <!-- ... -->
  </body>
</html>

Then in my code:

if (window.loaded) { run(); }
else { document.addEventListener("load", run); }

And that would achieve exactly what I want. Unfortunately, I cannot modify the HTML, which means that I am looking for a way to determine whether the document has loaded (not if the DOM is ready) from JS code only.

I have looked around quite a bit, but so far, all I have found revolves around DOMReady. Has no-one really ever looked for this?

Community
  • 1
  • 1
Félix Saparelli
  • 8,424
  • 6
  • 52
  • 67
  • In summary `DOMReady` isn't anywhere in the HTML5 spec, it's a term that means different things to the different people who implemented it before the HTML5 spec was fully developed. – Gareth May 26 '12 at 08:41

2 Answers2

5

As Dr.Molle points out, document.readyState contains the property you're after:

document . readyState

Returns "loading" while the Document is loading, "interactive" once it is finished parsing but still loading sub-resources, and "complete" once it has loaded.

The readystatechange event fires on the Document object when this value changes.

The order of event firing and readyState change is defined in the end of parsing section of the HTML5 spec. In summary:

  1. The document readyState is set to "interactive" as soon as parsing is complete.
  2. The DOMContentReady event is fired almost immediately (after it's determined which resources need to be loaded).
  3. Those resources are loaded.
  4. The document readyState is set to "complete" and the load event is fired.
Community
  • 1
  • 1
Gareth
  • 133,157
  • 36
  • 148
  • 157
  • I've removed some incorrect information from my post. DOMContentLoaded is not the same as `readyState="complete"`, as described in the [post-parsing](http://www.whatwg.org/specs/web-apps/current-work/#the-end) section of the HTML5 spec – Gareth May 26 '12 at 08:29
  • Indeed. So, I made this: https://gist.github.com/2792934. To summarise: `DOMContentLoaded` is runs when the DOM is loaded. `onload` runs after everything is loaded. `readyState` is set to `"complete"` just before that. Hence, you were both right, but I still have to wonder about all the different and ambiguous naming :) – Félix Saparelli May 26 '12 at 08:34
  • `DOMReady` wasn't ever an official term, but before the HTML5 spec got to the state it's currently in people needed a term to refer to. Now I guess a lot of the confusion comes from people mixing the correct term with the old name – Gareth May 26 '12 at 08:37
3

the onload-event of a window fires when the DOM and all ressources(scripts,images,stylesheets, etc.) have finished loading:

window.onload=function()
{
  //run code 
}
Dr.Molle
  • 116,463
  • 16
  • 195
  • 201