Skip to main content

Bug Tracker

Side navigation

#2069 closed bug (fixed)

Opened December 17, 2007 05:37PM UTC

Closed December 17, 2007 08:25PM UTC

ready issues

Reported by: joern Owned by:
Priority: major Milestone: 1.2.2
Component: core Version: 1.2.1
Keywords: Cc:
Blocked by: Blocking:

I've discovered two issues with 1.2.2b with the ready event:

For once, the event handler doesn't get a reference to jQuery anymore, instead only a (useless for me) event object is passed.


test("jQuery(function($) {})", function() {
	jQuery(function($) {
		equals(jQuery, $, "ready doesn't provide an event object, instead it provides a reference to the jQuery function, see");

The above test fails due to another issue: Binding a ready event after the event was issued doesn't do anything anymore. In 1.2.1 the handler would be triggered immediately. Though this behaviour isn't documented anywhere, but changing it definitely breaks stuff, so we should be the docs, too. Eg. adding this to

<p>If the handler is bound after the event already fired, it is triggered immediately.</p>

No idea how to fix it due to the new special event handling. An introduction to that would be great.

Attachments (1)
  • 2069.diff (2.1 KB) - added by davidserduke December 17, 2007 07:41PM UTC.

    possible patch

Change History (1)

Changed December 17, 2007 08:25PM UTC by brandon comment:1

resolution: → fixed
status: newclosed

Fixed in [4211].

The ready helper method and associated shortcuts act the same as they always have. Using the events API to bind/unbind/trigger the ready event on the document follows the standards within the events API.