javascript:how to write $(document).ready like event without jquery

Question

in jquery $(document).ready(function) or $(function) , how could I do the same thing without jquery, and I need browser compatiable, and allow to attach more than one function.

Note: dom ready!= window onload

I looked at the jQuery source code and there is quite a chunk of code related to the ready() handler. If I read the code correctly, the event is called `DOMContentLoaded`. IE does not support this, so `onreadystatechange` is used instead. — Šime Vidas, Oct 21 '10 at 15:52
Also, it has to do with `document.readyState` having the value `"complete"` — Šime Vidas, Oct 21 '10 at 15:54
@Šime Vidas: It has to do with many things (iframe loading has its own quirks? Who knew?), and quite frankly, it's an amazing piece of code. I was reminded why I no longer register events directly - it's a major PITA to do it *right*. — Piskvor left the building, Oct 21 '10 at 16:04
possible duplicate of [$(document).ready equivalent without jQuery](http://stackoverflow.com/questions/799981/document-ready-equivalent-without-jquery) — Roatin Marth, Oct 21 '10 at 16:58
I believe you are better off using jQuery than reinventing the wheel. It just has too many quirks (read browser compatibility issues) to think of — user, Oct 21 '10 at 17:49

Piskvor left the building · Accepted Answer · 2010-10-21T15:59:54.077

This is the way jQuery wraps the functions you're looking for - the snippet does not need jQuery, and is cross-browser compatible. I've replaced all calls to jQuery.ready() with yourcallback - which you need to define.

What goes on in here:

first, the function DOMContentLoaded is defined, which will be used when the DOMContentLoaded event fires - it ensures that the callback is only called once.
a check if the document is already loaded - if yes, fire the callback right away
otherwise sniff for features (document.addEventListener / document.attachEvent) and bind the callbacks to it (different for IE and normal browsers, plus the onload callback)

Lifted from jQuery 1.4.3, functions bindReady() and DOMContentLoaded:

/*
* Copyright 2010, John Resig
* Dual licensed under the MIT or GPL Version 2 licenses.
* http://jquery.org/license
*/
// Cleanup functions for the document ready method
// attached in the bindReady handler
if ( document.addEventListener ) {
DOMContentLoaded = function() {
    document.removeEventListener( "DOMContentLoaded", DOMContentLoaded, false );
    //jQuery.ready();
            yourcallback();
};

} else if ( document.attachEvent ) {
DOMContentLoaded = function() {
    // Make sure body exists, at least, in case IE gets a little overzealous 
            if ( document.readyState === "complete" ) {
        document.detachEvent( "onreadystatechange", DOMContentLoaded );
        //jQuery.ready();
                    yourcallback();
    }
    };
}

// Catch cases where $(document).ready() is called after the
// browser event has already occurred.
if ( document.readyState === "complete" ) {
    // Handle it asynchronously to allow scripts the opportunity to delay ready
//return setTimeout( jQuery.ready, 1 );
    // ^^ you may want to call *your* function here, similarly for the other calls to jQuery.ready
    setTimeout( yourcallback, 1 );
}

// Mozilla, Opera and webkit nightlies currently support this event
if ( document.addEventListener ) {
    // Use the handy event callback
document.addEventListener( "DOMContentLoaded", DOMContentLoaded, false );
// A fallback to window.onload, that will always work
//window.addEventListener( "load", jQuery.ready, false );
    window.addEventListener( "load", yourcallback, false );
 // If IE event model is used
 } else if ( document.attachEvent ) {
        // ensure firing before onload,
        // maybe late but safe also for iframes
        document.attachEvent("onreadystatechange", DOMContentLoaded);

        // A fallback to window.onload, that will always work
        window.attachEvent( "onload", yourcallback );

 }

That's 51 lines of pure JavaScript code, just to register the event reliably. As far as I know, there is no easier method. Goes to show what the wrappers like jQuery are good for: they wrap the capability sniffing and ugly compatibility issues so that you can focus on something else.

I gotta say it's a lot of complicated code for knowing when to initialize your scripts that use the DOM... Like I posted in my answer, I just call a single initializer function from after the close body tag — Juan Mendes, Oct 22 '10 at 22:15
@Juan Mendes: Yes, that does something superficially similar - but inline script tags have their quirks, too: blocking parallel downloads in *cough cough* certain browsers, for example. And don't forget the whole "let's modify the DOM while it's still loading" barrel of fun. That's why I'd rather go with $.ready() - one well-cached library on Google's CDN and one well-working function call later, It Just Works. But if you want to reinvent all the JS hacks since 1997, go right ahead. — Piskvor left the building, Oct 22 '10 at 22:36
@Piskvor: "But if you want to reinvent all the JS hacks since 1997, go right ahead"? How is this a hack? I think it's a simple (elegant) solution. You're guaranteed that the DOM is ready if you place a script tag after the body tag, it's not "let's modify the DOM while it's still loading" — Juan Mendes, Oct 22 '10 at 22:52
@Juan Mendes: I've misread your comment - are you saying "let's deliberately break web standards?" `
anything that's not whitespace — Piskvor left the building, Oct 22 '10 at 23:01
@Piskvor. I didn't know that adding a script tag after the body tag triggered QM. Can you point me to a resource with further information? By the way your 'smart' comments are assuming things that I didn't say, I never said that triggering QM was elegant and I never said that you should modify the DOM while it's loading, please be more courteous with replies. — Juan Mendes, Oct 22 '10 at 23:13
Can you point me to something that talks about quirks mode and scripts at the bottom of the page? http://developer.yahoo.com/performance/rules.html is the link that suggests you should always leave your scripts at the bottom of the page. — Juan Mendes, Oct 26 '10 at 22:33

shawndumas · Answer 2 · 2013-02-26T18:14:10.193

9

Smallest DOMReady code, ever.

<html>
  <head>
    <script>
      var ready = function (f) {
        (/complete|loaded|interactive/.test(document.readyState)) ?
            f() :
            setTimeout(ready, 9, f);
      };
    </script>
  </head>
  <body>
    <script>
      ready(function () {
        alert('DOM Ready!');
      });
    </script>
  </body>
</html>

edited Feb 26 '13 at 18:14

answered Aug 11 '11 at 13:41

shawndumas

1,319
13
17

Quick question: what is the "r" function? I get an error when trying this in FF. – Aerik May 25 '12 at 22:23
note that this uses `eval()` under the hood. But cool trick man! – Camilo Martin Oct 03 '12 at 19:17
1

use "setTimeout(ready, 9, f)" if you are not in ie or "setTimeout(function () { ready(f); }, 9)" if you are – shawndumas Dec 06 '12 at 22:34
Your condition is reversed. – the system Feb 18 '13 at 23:41

score 3 · Answer 3 · answered Apr 30 '13 at 06:35

This is all you need if you're supporting IE9+ and modern (2013) versions of Chrome, FF, Safari, etc.

function ready(event) {
    // your code here
    console.log('The DOM is ready.', event);
    // clean up event binding
    window.removeEventListener('DOMContentLoaded', ready);
}

// bind to the load event
window.addEventListener('DOMContentLoaded', ready);

score 2 · Answer 4 · answered Oct 21 '10 at 18:15

Here's a method I use that seems to work reliably

function ready(func) {
  var span = document.createElement('span');
  var ms = 0;
  setTimeout(function() {
    try {
      document.body.appendChild(span);

      document.body.removeChild(span);

      //Still here? Then document is ready
      func();
    } catch(e) {
      //Whoops, document is not ready yet, try again...

      setTimeout(arguments.callee, ms);
    }
  }, ms);
}

Pretty simple, it just keeps trying to append an empty <span> element to document.body. If the document is not "ready" an exception will be thrown, in which case it tries again with a new setTimeout call. Once no exception is thrown, it calls the callback function.

I'd be happy to hear if there are any problems with this method. It has worked well for me, but I have not done the extensive testing that would be natural to any popular Javascript framework.

Two words: memory leaks. On older browsers, with all the element adding and removing, you'll be leaking memory like crazy. Plus, you're reimplementing the busy-wait loop in JavaScript (which is not the most efficient language as it is). — Piskvor left the building, Oct 22 '10 at 22:52
I'm not seeing it. With this method, an element is only added and removed once, when the document is ready. And even then only one element is created in memory outside the timeout function. Also, `setTimeout/setInterval` with 0 ms delay is not the same as a conditional while loop. With the way timers work in JS, and the simplicity of the operations within the timeout function of this example, performance should not be significantly affected. — MooGoo, Oct 23 '10 at 20:57

score 1 · Answer 5 · answered Oct 21 '10 at 17:45

1

I've seen lots of different ways of trying to do this. The simplest way (suggested by yahoo initially, I think) is to just call your initializer function after the close body tag, a bit obtrusive, but it's a single line.

answered Oct 21 '10 at 17:45

Juan Mendes

80,964
26
138
189

score 0 · Answer 6 · answered Jul 24 '14 at 02:07

I have this after the 'close body' tag and before the 'close html' tag. and it works pretty well. The load presets function assigns width,height and position values to css div tags. useful for different screen sizes.

document.onreadystatechange = function () {
if  (document.readyState == "interactive") {
loadPresets();
}

}

score 0 · Answer 7 · edited May 23 '17 at 10:29

Edit

The DomReady event does not exist nativly in javascript. You can implement your own by following some wonderful work done by people like Dean Edwards here and here with those in place you can perform a similar event attachment process on document instead of window.

Check out user83421's answer to How do I add an additional window.onload event in Javascript

To recap here as well.

if (window.addEventListener) // W3C standard
{
  window.addEventListener('load', myFunction, false); // NB **not** 'onload'
} 
else if (window.attachEvent) // Microsoft
{
  window.attachEvent('onload', myFunction);
}

The snippet you have is just for the load event – Juan Mendes Apr 05 '11 at 21:27 — Juan Mendes, Apr 05 '11 at 21:27

javascript:how to write $(document).ready like event without jquery

Note: dom ready!= window onload

7 Answers7

Edit

Linked