Closed
Bug 412418
Opened 17 years ago
Closed 15 years ago
Synchronous XMLHttpRequest interferes with setTimeout
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 340345
People
(Reporter: bugs+mozilla, Unassigned)
References
()
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.12pre) Gecko/20080105 Camino/1.6b1pre (like Firefox/2.0.0.12pre)
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b3pre) Gecko/2008011404 Minefield/3.0b3pre
I'm running a lot of timeouts with delay of 0ms. The timeout method performs a synchronous XHR. More than half of the time, the next timeout is fired when the XHR loads, instead of continuing the execution of the first timeout method.
I've verified the issue on Mac OS X 10.5.1 and on Ubuntu Linux, with the Firefox nightly build from January 14th, 2008.
Reproducible: Always
Steps to Reproduce:
1. Schedule two timeouts at 0ms delay
2. Make sure the first timeout performs a synchronous XHR
Actual Results:
Observe that the second timeout is fired before the first timeout has finished execution.
Expected Results:
The first timeout finishes execution, and only then the second timeout is fired.
Reporter | ||
Comment 1•17 years ago
|
||
Comment 2•17 years ago
|
||
> DOM:Mozilla Extensions, dupe of bug 340345 ?
Assignee: general → nobody
Component: JavaScript Engine → DOM: Mozilla Extensions
QA Contact: general → general
Updated•17 years ago
|
Summary: Synchronous XMLHttpRequest interfers with setTimeout → Synchronous XMLHttpRequest interferes with setTimeout
Simple example, should alert 1,2,3,4, works in Firefox 2 and IE 6 and 7, in Firefox 3 alerts 1,4,2,3
Yeah, dupe of DOM:Mozilla Extensions, dupe of bug 340345
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•12 years ago
|
Component: DOM: Mozilla Extensions → DOM
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•