Closed Bug 454583 Opened 16 years ago Closed 16 years ago

Mousemove events can fire during synchronous XMLHttpRequest, violating run-to-completion model

Categories

(Core :: DOM: Core & HTML, defect)

x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 333198

People

(Reporter: sjoerdmulder, Unassigned)

Details

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1

When listening to the mousemove event, normally every event fired will only fire when the previous event is finished even when having synchronous XMLHttpRequest. But in Fx 3.0.1 this is not the case anymore when an XMLHttpRequest is inside the execution

Reproducible: Always

Steps to Reproduce:
1. Open attached file
2. Jank your mouse, the mousemove coordinates should appear
3. The message "This should not be possible" appears one or multiple times
Actual Results:  
In all browser except Fx 3 the message "This should not be possible" does not appear (as it should be). This should be the result


This is very annoying for AJAX toolkits, which use JIT mechanisms to dynamically load extra javascript.
Dup of bug 340345?
Assignee: general → nobody
Component: JavaScript Engine → DOM: Mozilla Extensions
QA Contact: general → general
Summary: Javascript execution is not single-threaded anymore Fx 3 → Mousemove events can fire during synchronous XMLHttpRequest, violating run-to-completion model
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Component: DOM: Mozilla Extensions → DOM
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: