Skip to main content

Bug Tracker

Side navigation

#7279 closed bug (fixed)

Opened October 22, 2010 04:09AM UTC

Closed April 01, 2011 12:12AM UTC

Last modified March 14, 2012 02:28AM UTC

.bind("ready") events fire out of order

Reported by: john Owned by: dmethvin
Priority: high Milestone:
Component: event Version: 1.4.3
Keywords: needsreview Cc:
Blocked by: Blocking:

Test case by Ben Alman here:

See also: #7247

Attachments (0)
Change History (7)

Changed October 22, 2010 04:09AM UTC by john comment:1

component: unfiledevent
priority: undecidedhigh

Changed October 23, 2010 08:12AM UTC by snover comment:2

status: newopen

Changed October 30, 2010 03:34PM UTC by cowboy comment:3

Sent a pull request with a possible fix (And a ton of unit tests)

Changed November 19, 2010 07:35PM UTC by addyosmani comment:4

keywords: → needsreview

Changed November 21, 2010 10:44PM UTC by snover comment:5

owner: → cowboy
status: openassigned

Changed March 31, 2011 07:08PM UTC by cowboy comment:6

owner: cowboydmethvin

Changed April 01, 2011 12:12AM UTC by dmethvin comment:7

resolution: → fixed
status: assignedclosed

We have now documented that .bind("ready", ...). fires after ..ready().