Detect if a Document Has Loaded with JavaScript
If you follow me on Twitter, you've probably noticed me whining about ChromeDriver. For some reason it seems as though tests run before the document has properly loaded, leading to transient test failures and loads of frustration.
I thought the best way to avoid these problems was to ensure the document had loaded before each test run -- that way there's no excuse for transient loading problems. Here's the snippet I use to check if the page is ready:
// The basic check
if(document.readyState === 'complete') {
// good to go!
}
// Polling for the sake of my intern tests
var interval = setInterval(function() {
if(document.readyState === 'complete') {
clearInterval(interval);
done();
}
}, 100);
I found it ironic that for years we went looking for the ultimate "domready" script and here I am in 2015 trying to figure out if the document has completed loading. This is why we drink.
![An Interview with Eric Meyer]()
Your early CSS books were instrumental in pushing my love for front end technologies. What was it about CSS that you fell in love with and drove you to write about it?
At first blush, it was the simplicity of it as compared to the table-and-spacer...
![Create Namespaced Classes with MooTools]()
MooTools has always gotten a bit of grief for not inherently using and standardizing namespaced-based JavaScript classes like the Dojo Toolkit does. Many developers create their classes as globals which is generally frowned up. I mostly disagree with that stance, but each to their own. In any event...
![Build a Slick and Simple MooTools Accordion]()
Last week I covered a smooth, subtle MooTools effect called Kwicks. Another great MooTools creation is the Accordion, which acts like...wait for it...an accordion! Now I've never been a huge Weird Al fan so this is as close to playing an accordion as...
![MooTools Flashlight Effect]()
Another reason that I love Twitter so much is that I'm able to check out what fellow developers think is interesting. Chris Coyier posted about a flashlight effect he found built with jQuery. While I agree with Chris that it's a little corny, it...
Between
DOMContentLoaded/loadanddocument.readyState, I think that there are a few ensure that something is executed once the document is loaded.HTMLDocument.prototype.ready = function () { return new Promise(function(resolve, reject) { if (document.readyState === 'complete') { resolve(document); } else { document.addEventListener('DOMContentLoaded', function() { resolve(document); }); } }); } document.ready().then(...);Nice, Chris!
Thanks. I think you may have posted something very similar to this before. Or am I just imagining that?
window.onload = function () { alert("keep it oldschool!") };I must be missing something obvious … why not just use jQuery?
You don’t use jQuery for a tiny code snippet…
Re use is cultural fenomenon Unless this is some kind of deep JavaScript master class? Which I think it is not.
We have solved and debated this issue in 2008 last time.
As I like to reuse what is shareable, I might point to this (instead of re writing it all over again).
No it was 2006 sorry … Very interesing page to read now.
I suggest read it all, including comments, than come back here.
Personally, I will prefer js and only include jQuery if there is a strong need and justification for that. But that’s me, you might prefer to use jQuery, but i don’t think there is a need to get pissed for using js instead of jquery
Alternately, I think you could use the
ReadyStateChangeEvent.document.addEventListener('readystatechange', function docStateChange(e) { if(e.target.readystate === 'complete') { e.target.removeEventListener('readystatechange', docStateChange); done(); } });A few people mentioning using an event listener. The problem is that I don’t know if the page is done loading; i.e. I can’t count on an event listener. Polling is the best way if I don’t know when my script is being injected.
Could you clarify this a litte? Using polling here seems a bit crude in comparison to replacing it with listening for a
readystatechangeevent.If my test is triggered after the page is ready (remember, I can’t count on when it starts), readystatechange will have already triggered and my signal will never be triggered.
But wouldn’t that be covered by your basic test already? So…only bind a listener in case the
readyStateisn’tcompleteyet?Maybe a combination of the two would suit
if(document.readyState !== 'complete'){ // use Kevin's addEventListener('readystatechange', .... }This is the version that I am using at the moment, I don’t know if it applies to your test though..
// This is needed to prevent onreadystatechange being run twice var ready = false; document.onreadystatechange = function() { if (ready) { return; } // interactive = DOMContentLoaded & complete = window.load if (document.readyState == 'interactive' || document.readyState == 'complete') { ready = true; // init you code here } };How can i use this for a preloader?
jQuery code is:
$(window).load(function(){$('#preloader').fadeOut();});but i will use it without jQuery…
thanks! worked perfectly for my case where no events seem to work as well. just wanted a script for console or bookmark which would keep scrolling down on infinite scrollers. it surely still can be improved, but this was good enough for me for now:
window.scrollTo(0,document.body.scrollHeight) if (interval) { clearInterval(interval) interval = null } else var interval = setInterval(function() { console.log(document.readyState) if(document.readyState === 'complete') { window.scrollTo(0,document.body.scrollHeight) /* setTimeout(function() { if(document.readyState === 'complete') clearInterval(interval) }, 100)*/ } }, 200)if (document.readyState === 'complete')Yep, that worked for me. Tough to find because there’s way more out there on the event ‘ready’ as opposed to the state ‘ready’.