i've also had issues with this, not only in ie but sometimes in firefox too.. and ie 6&7 occasionally crashed or couldn't load the page when using $().ready() so now i just call the init function from the footer of the page.. i know it's kind of ugly but it works every time and doesn't crash :)..
oh and it sometimes happens for me on http://jquery.com/api too ($().ready not firing - both in ie6&7 and firefox2).. dennis. Jack Killpatrick wrote: > FWIW, I've had issues in IE 6/7 with $(document).ready() not firing > something in it's function. I've never dug into exactly why it happens, > but found a workaround using setTimeout, like this: > > $(document).ready(function() { > setTimeout( > function(){ > your code that isn't firing in IE here > } > , ( $.browser.msie ) ? 500 : 0 > ) > }); > > So, maybe give that a try. FWIW, we (me and the folks I work with) found > that 500ms seemed to do the trick, but 100ms didn't. > > Also, If anyone knows why that's needed for some things to fire via > $(document).ready, I'd love to know. We've also worked around it by > doing these things: > > 1. putting our $(document).ready at the end of the HTML page (after the > objects that we need ready). > 2. used setTimeout() to check for the presence of the object(s) we need > ready, and when they become ready, binding to them. > > - Jack > _______________________________________________ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
