Multiple simultaneous requests in IE7/8 fail about 25% of the time

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create multiple simultaneous requests (about 4) in IE7/8
2. See that the response object sent to the success callback is not always for 
the correct call.

What is the expected output? What do you see instead?

I'm expecting that the success callback is being passed the correct data for 
the intended call. For example, if I make four requests to A,B,C and D and I am 
expecting a,b,c and d as a response, sometimes I'll get back response d for 
request A, etc.

What version of the product are you using? On what operating system?

2.0.2. IE7/8. Windows XP

Please provide any additional information below.

I've provided a test script. You may need to run it a few times, but it will 
fail in IE7/8 eventually. I've tried this on various machines.

If you have any questions, please feel free to contact me at either of the 
addresses, thanks.

weters@me.com (my primary e-mail)
weters19@gmail.com (my gmail account for submitting this report)

Thanks,
Tom Peters

Original issue reported on code.google.com by weter...@gmail.com on 15 Jun 2010 at 8:10

Attachments:

• jsonp-2.0.2-bug.txt

[GoogleCodeExporter]

It appears that this issue didn't exist with 1.1.4. I swapped it out and it 
appears to work. So it looks like it's something introduced in 2.0.x.

Original comment by weter...@gmail.com on 15 Jun 2010 at 8:21

[GoogleCodeExporter]

Interesting. I stress-tested this thing but apparentely not enough :(

I have a fallback solution for IE that was removed during early stages of 
2.0.x. Seems like I'll have to use it finally. Testing as we speak.

Original comment by aubourg.julian on 16 Jun 2010 at 2:18

• Changed state: Accepted
• Added labels: Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Fixed as of 2.1.0.

I simply back-ported the htmlFor/event/onclick trick back in and I can't make 
your test script fail any longer (IE8, Vista). BTW, I put your script in the 
repository with a comment thanking you for it if that's ok with you.

I thought I could rely on onreadystatechange being fired as soon as possible 
but I should know better and never EVER trust anything the IE team does.

Let me know of any side effect in other browsers (there shouldn't be any but 
you never know).

Original comment by aubourg.julian on 16 Jun 2010 at 2:48

• Changed state: Fixed

[GoogleCodeExporter]

Looks like it's working. Thanks for the quick turnaround.

> BTW, I put your script in the repository with a comment thanking you for it 
if that's ok with you.

Not a problem. Glad to help.

Original comment by weter...@gmail.com on 16 Jun 2010 at 1:54