"Arnar Birgisson" <[EMAIL PROTECTED]> writes: > Have you tried simply "callLater(0, func)"? That should execute the function > in the next event loop, and I assume IE finishes all rendering/dom > manipulation before invoking javascript events. > > I'm not 100% sure though, in the browsers js implementation, setTimeout(..., > 0) might be handled as a special case and run right away. I doubt it though.
Hi Arnar! It doesn't work. I've lowered it up to 0.3 seconds and it started giving me errors so I had to raise it back to 0.5 seconds and sometimes to 1s depending on how much data can be returned as the result of the JSON call... Actually, I haven't tried setting the value to zero, but it didn't work with 0.3s, so I stopped trying to lower it. It looks like IE fires the event right after it has the result but before it renders it and can, e.g., retrieve the value of the selected option (following with my SELECT+OPTION example). With this I could also try setting a hidden field and force some artificial value to be set by default, but I would like to avoid that as much as possible. -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~----------~----~----~----~------~----~------~--~---
