I would be honored to have my work represented in a book. Thanks for the consideration!

Many thanks for getting back so quickly, and yep you’ve sure answered my question! I hadn’t taken it in properly that you’re passing a function into the onDOMReady. I’ll have to delve into this in more detail, it’s a bit of a revelation to me, but sounds a great technique to keep things out of the global context. Sounds like you’ve really got something here )

If I am understanding your question correctly, the function is able to fire because it is still within the context of the onDOMReady function, any function definitions (fireDOMReady) that reside within that context are part of the scope chain and therefore have access to all variables at any level equal to or higher than its own. The event handlers hold a reference to fireDOMReady which in turn holds a reference to the user-provided function.

I am not to sure what your eluding to with this; “things will only fire if, say onload, is placed outside the function (ie globally).” But I can tell you, that onDOMReady can be called within any context, but it is important to note it can only be called once per page (I hope to upgrade this ability in the future to unlimited calls). It is typically best to pass the function directly to the method rather than a reference to avoid polluting the global namespace:

onDOMReady(function(){
//do something
})

I hope this answers your question!

The code is still the same but to be honest, I haven’t looked at it in a while, so perhaps some tweaking is in order. Although I had initially created an alternate version which employed a deferred script instead of Diego Perini’s doScroll hack for IE.

Now that I think about it, I had planned on adding the ability to call the function multiple times with multiple callbacks rather than just once.

As per browser support, I have tested the method to success in IE6+, FF2+, Opera 9+, Safari 2+, and Chrome 1+ but haven’t been able to get my hands on any older browsers so I can’t be too sure. However, the function should degrade gracefully to window.onload in any browsers that do not support the more advanced methods the script utilizes thanks to the lack of browser detection.