|
|
Posted by Tim Streater on 08/07/07 09:23
In article <Xns998513C37187Dnanopandaneredbojias@198.186.190.161>,
Neredbojias <monstersquasher@yahoo.com> wrote:
> Well bust mah britches and call me cheeky, on Tue, 07 Aug 2007 06:20:29 GMT
> mjones scribed:
>
> > Thanks for the menu example Bergamot. I'm not a fan of the expanding/
> > contracting type of menu, however. It makes me motion sick, but I
> > know many like it. I call it mystery meat - you don't know what's
> > there until you mouse over or click.
> >
> > I guess that's a no then on my original request.
> >
> > I appreciate all your comments and ideas.
> >
> > Thanks all and good night,
>
> I see the sign of the cause of the original problem. The content is being
> delayed in loading (-include? -iframe? -javascript manipulation?) so
> there is nothing "there yet" when the hash, #demarco, tries to operate.
> When the content finally does appear, it's too late.
Loading stuff in frames or iframes does take time, a problem especially
if other frames rely on the loaded information. I got round this sort of
problem by having the onLoad event of the slow-loading frame set a flag.
You can use a timer event elsewhere to pick this up. Unfortunately you
need to do this in a loop as JS doesn't give you the proper tools, but
at least you can avoid running the CPU at 100% by not simply spinning on
the flag.
Navigation:
[Reply to this message]
|