#7279 - .bind("ready") events fire out of order

[cowboy]

My changes fix the issue described in this ticket. Here's an updated JSFiddle using my local build.

I basically check to see if the bind subsystem exists, and if it does, use rootjQuery.bind( "ready", fn ) otherwise just use readyList.push( fn ).

I also added a bunch of unit tests, so if nothing else you should grab those.

Hope this helps!

[cowboy]

BTW, I consider this a temporary fix. I really think that the DOM ready event system should really get an overhaul to avoid issues like these in the future.. but I don't know that the overall behavior (which my changes address) needs to wait until 1.5.

[dmethvin]

Ben, the ready code is most likely being replaced by the Deferreds implementation from jaubourg, so all of this is getting an overhaul. From the discussion in the ticket and the code it seems like the two major issues were that some handlers were firing multiple times (fixed in DOM0 already) and also that handlers fired out of the order they were attached. Anything else?

[cowboy]

The big issues I had were that:

• some bound handlers were firing twice (already fixed).
• unlike other "event shortcut" methods, $.fn.ready isn't a shortcut for $.fn.bind, which isn't a problem by itself, but these confusing side effects arise...
• bound handlers can fire out-of-order, depending on which method is used to bind them.
• when fn is called in $( fn ) and $(document).ready( fn ), a reference to jQuery is passed, but when fn is called in $(document).bind( "ready", fn ), an event object is passed.

[dmethvin]

Ben, I suspect several of these issues are already resolved in 1.5.2, but can you review and see what might be left? I'm trying to figure out if #7279 should be closed or not.

[cowboy]

Added a replacement pull #293, killing this one.