Skip to main content

Bug Tracker

Side navigation

#3988 closed bug (fixed)

Opened January 25, 2009 08:33PM UTC

Closed November 10, 2009 02:51PM UTC

$(document).ready() fires after images load in IE

Reported by: tommcfarlin Owned by:
Priority: major Milestone: 1.3.2
Component: core Version: 1.3.1
Keywords: Cc:
Blocked by: Blocking:

In IE, $(document).ready() fires after images are fully loaded. This was not a problem in version 1.2.6.

Example code:

$(function() {

$('container').children('img').each(function() {




In IE7 with 1.2.6, all images will be hidden before the page loads. With 1.3, images load _then_ then the ready event fires.

Attachments (0)
Change History (7)

Changed January 26, 2009 07:34PM UTC by Webdawson comment:1

Its a Bug in IE6 and IE7. Here's an example:

Changed January 28, 2009 10:43PM UTC by john comment:2


This was due to #2614 and #3880 - there were definite problems with the code in 1.2.6, in 1.3 - and now a different set of problems in 1.3.1.

A larger discussion here:

I just landed a fix for this in SVN rev [6170].

I just pushed up a new nightly that you can use until 1.3.2 final comes out.

Changed February 20, 2009 01:21PM UTC by john comment:3

resolution: → fixed
status: newclosed

Changed August 17, 2009 04:35PM UTC by drewcovi comment:4

resolution: fixed
status: closedreopened

I'm seeing this issue as resurfaced with safari 4, correct me if i'm wrong.

Changed August 18, 2009 12:11AM UTC by dmethvin comment:5

drewcovi, do you have a test case?

Changed August 18, 2009 03:01PM UTC by drewcovi comment:6


seems like I can only replicate it on a "page reload" situation. if we need a test case for this circumstance I certainly can make one. I would say its a low priority bug as refreshing a page will cause the behavior but is not as common.

thoughts? I'm willing to create the testcase if we think this is a valid concern.

Changed November 10, 2009 02:51PM UTC by davidserduke comment:7

resolution: → fixed
status: reopenedclosed

The reported problem (in IE with 1.3.1) was fixed and closed. If you are seeing a similar problem with Safari you'd like to report go ahead and make that test case and open a new ticket. As for me, if it is some timing issue in the page load where you have to click reload to get it to happen I suspect it would be low priority as well.