On Wed, 15 Aug 2007 15:20:17 -0700, "Erik Beeson" <[EMAIL PROTECTED]> wrote:
> What I'm saying is, window.load is like your "reallydone". It happens after
> all of the document.ready stuff is done. I suggest you do all of your
> hooking up stuff in document.ready, and do the animations in window.
What I'm saying is, window.load is like your "reallydone". It happens after
all of the document.ready stuff is done. I suggest you do all of your
hooking up stuff in document.ready, and do the animations in window.load.
You can keep content from flashing by hiding it in a document.ready, or even
be
Well, they start by hiding various page elements and then fading them back in,
sometimes in weird ways. So I need the hiding part to happen as soon as
possible so that there's no "flicker of content". document.ready() hasn't
caused me any problems in that regard so far when the animations ar
You might try moving your opening animations to $(window).load(function()
{...});
--Erik
On 8/15/07, Larry Garfield <[EMAIL PROTECTED]> wrote:
>
>
>
> Good jQuery.
>
> I have a site where I have a series of animations that need to run on
> load. I also have a large number of other events that
4 matches
Mail list logo