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.
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...
Before we get started, it's worth me spending a brief moment introducing myself to you. My name is Mark (or @integralist if Twitter happens to be your communication tool of choice) and I currently work for BBC News in London England as a principal engineer/tech...
I released my first MooTools class over a year ago. It was a really minimalistic approach to zebra tables and a great first class to write. I took some time to update and improve the class.
The XHTML
You may have as many tables as...
Front-end developing is beautiful, and it's getting prettier by the day. Nowadays we got so many concepts, methodologies, good practices and whatnot to make our work stand out from the rest. Javascript (along with its countless third party libraries) and CSS have grown so big, helping...
Between
DOMContentLoaded
/load
anddocument.readyState
, I think that there are a few ensure that something is executed once the document is loaded.Nice, Chris!
Thanks. I think you may have posted something very similar to this before. Or am I just imagining that?
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
ReadyStateChange
Event.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
readystatechange
event.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
readyState
isn’tcomplete
yet?Maybe a combination of the two would suit
This is the version that I am using at the moment, I don’t know if it applies to your test though..
How can i use this for a preloader?
jQuery code is:
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:
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’.