- From: Jonas Sicking <jonas@sicking.cc>
- Date: Mon, 9 Mar 2009 17:25:25 -0700
On Mon, Mar 9, 2009 at 5:11 PM, Drew Wilson <atwilson at google.com> wrote: >> >> >> > and most important >> > 3) why it did actually happen in my code? (using an async XHR) >> >> Not sure what you are saying here. Do you have example code. > > I think what he's talking about the issue described at > http://www.nerdgod.com/ie7test2.html. > > I was CC'd on an email thread about this last year - IE can sometimes call > xhr callbacks at inappropriate times (like when in the middle of a JS > function call). Summarizing the thread, it seems that invoking certain JS > functions in IE (like alert()) can cause IE to re-enter the message loop and > start processing messages which can cause things like XHR request callbacks > to be invoked. > > I'm pretty sure this is better classified as a bug in IE rather than as > expected JS language behavior, though. Same thing can happen in Firefox 3. We also consider it a bug though and would like to get it fixed. It is non-trivial to fix though, but Firefox 3.1 has some improvements. / Jonas
Received on Monday, 9 March 2009 17:25:25 UTC