Open Bug 951805 Opened 11 years ago Updated 2 years ago

Alert does not block UI thread execution

Categories

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

25 Branch
defect

Tracking

()

UNCONFIRMED

People

(Reporter: droberge, Unassigned)

Details

Attachments

(2 files, 1 obsolete file)

Attached file multi-alert.html (obsolete) —
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36

Steps to reproduce:

1. Create global variable, e.g. var tmp = 1
2. Create, open and send an XHR with a onreadystatechange handler that modifies the global variable when the readyState equals 4. Assume the XHR takes some time to complete (e.g. 3 seconds)
3. While the XHR is in progress, display an alert dialog
4. Leave dialog open until XHR completes
5. Close dialog, and open another alert dialog with the global variable value


Actual results:

The global variable is modified between the first alert showing and the second alert showing. It's as if the onreadystatechange handler is executed concurrently on the UI thread while the alert is showing


Expected results:

I feel the onreadystatechange handler should not be executed until the current javascript execution completes, e.g. both alerts are displayed and closed.
Attached file slow-server.py
Attached file multi-alert.html
Attachment #8349591 - Attachment is obsolete: true
Component: Untriaged → DOM: Core & HTML
OS: Windows 7 → All
Product: Firefox → Core
Hardware: x86_64 → All
Dup of some old bug. Alert runs in the same thread as the page. 
Multiprocess FF will help here.
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046

Move all DOM bugs that haven't been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.
Priority: -- → P5
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: