rakesh makluri Reporter
	Description • 12 years ago

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.30 Safari/536.5

Steps to reproduce:

1.Unzip the attached content in to the Web folder
2.Launch the XMLHTTPSynchronousTest.htm through the URL


There are two synchronous request for the same file which is in the webserver, from different iframes. Request sent in onload of the iframe content.



Actual results:

FF is firing the second request from the other iframe even though the response is not received for the first request which is synchronous.

You can check the timings of the request fired and response received for both the requests. You can even check in HTTPWatch.

non-FF browser working as expected.


Expected results:

It should wait until the response received for the first request and then fire the second request.

	Alice0775 White
	Comment 1 • 12 years ago

Last good;
10-May-2006 0349
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9a1) Gecko/20060510 Minefield/3.0a1

First bad;
10-May-2006 1447
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9a1) Gecko/20060510 Minefield/3.0a1

Bonsai log:
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2006-05-10+00%3A00%3A00&maxdate=2006-05-10+15%3A00%3A00&cvsroot=%2Fcvsroot

	Boris Zbarsky [:bzbarsky]
	Comment 2 • 12 years ago

Yep.  A "sync" XHR is actualy a nested event loop; events can still happen on other pages.

	satya
	Comment 3 • 12 years ago

Hi Mozilla, please fix it. Its decreases the performance.

	rakesh makluri Reporter
	Comment 4 • 12 years ago

Even though events fired on other pages(within in the same parent window), another XHR should wait until the response(synchronous) received.

What if the code in another page is dependent on the response received from XHR sync request?

(In reply to Boris Zbarsky (:bz) from comment #2)
> Yep.  A "sync" XHR is actualy a nested event loop; events can still happen
> on other pages.