Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>To add to HurnsMobile's excellent answer; Looking at <code>bindReady()</code>, which is the internal call that jQuery makes to bind to the document load event every time you call <code>$(some_function)</code> or <code>$(document).ready(some_function)</code> we see why we cannot bind to <code>"ready"</code>:</p> <pre><code>bindReady: function() { if ( readyBound ) { return; } readyBound = true; // Catch cases where $(document).ready() is called after the // browser event has already occurred. if ( document.readyState === "complete" ) { return jQuery.ready(); } // 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 ); // 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", jQuery.ready ); // If IE and not a frame // continually check to see if the document is ready var toplevel = false; try { toplevel = window.frameElement == null; } catch(e) { //and silently drop any errors } // If the document supports the scroll check and we're not in a frame: if ( document.documentElement.doScroll &amp;&amp; toplevel ) { doScrollCheck(); } } } </code></pre> <p>To sum it up, <code>$(some_function)</code> calls a function which binds to:</p> <ul> <li>DOMContentLoaded</li> <li>onreadystatechange (DOMContentLoaded)</li> <li>window.load / onload</li> </ul> <p>Your best bet would be to bind to those actions that might <em>create</em> new <code>.tooltipper</code> elements, rather than trying to listen for the ready event (which happens only once).</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload