On Oct 7, 3:56 pm, "Iván N Paz" <[EMAIL PROTECTED]> wrote: > Why not move everything into DomReady????
What I meant was add the final DomReady event as a fn.delay(10) just to help ensure the other parts of the chain execute first. I don't know if they're executed in order or concurrently, thus the delay recommendation. Plus, if you have page-specific script sections generated by your backend then you may not be using DomReady in them, though I admit that would be easy to remedy. > Using delays may solve this issue in some machines, but not in others, > since you dont have control on network bandwidth and/or processor > speed on the end machine... Given what I said above, the whole DOM must be loaded including all the javascript and css. Thus if you delay its execution by 10, it should fire after most the other DomReady events if they are fired concurrently. If paranoid you could do 100 or 200. ;-) Regards, Flea
