Bug Tracker

Opened 14 years ago

Closed 13 years ago

#3988 closed bug (fixed)

$(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.

Change History (7)

comment:1 Changed 14 years ago by Webdawson

Its a Bug in IE6 and IE7. Here's an example: http://www.kollermedia.at/jquery_bug.html

comment:2 Changed 14 years ago by john


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: http://groups.google.com/group/jquery-dev/browse_thread/thread/3abf45d3fd4d50fc

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. http://code.jquery.com/nightlies/jquery-2009-01-28.js

comment:3 Changed 14 years ago by john

Resolution: fixed
Status: newclosed

comment:4 Changed 13 years ago by drewcovi

Resolution: fixed
Status: closedreopened

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

comment:5 Changed 13 years ago by dmethvin

drewcovi, do you have a test case?

comment:6 Changed 13 years ago by drewcovi


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.

comment:8 Changed 13 years ago by davidserduke

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.

Note: See TracTickets for help on using tickets.