Just to clarify, IEContentLoaded is an IE specific method based on MS information and at the time of publishing (and jQuery inclusion) it was known to not work for iframes (the reason is still unknown to me though).

This is the reason I use the “onreadystatechange” event on IE if the target of the check is an iframe while I use the “doScroll()” trick on the main document.

I never suggested to use my method alone, since it was released the IEContentLoaded page clearly states:

meant to be used as an IE alternative in other fine scripts trying to fix the window onload problem

and link to other developer’s scripts that you also mention in your test and description.

There is nothing bad in mixing those scripts, for example use the “doScroll()” for the main document and the HTC method or Dean/Mathias document.write for iframes.

In other words it is up to the implementors to spice or cut their methods depending on their libraries/framework needs.

IEContentLoaded, as of today, is correctly implemented as I originally intended only in jQuery, Prototype, ExtJS and in both sIFR and SwfObject.

I would add “BrotherCake” body detection to your list of methods since that is really the only needed cross-browser moment if you just need to attach your widgets to the body.

Keep up the good work,

Diego