418493 - setTimeout() blocked by alert() in Firefox 3

Status: RESOLVED INVALID

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

Description

[Mark Smith [:mcs]]

Attachment: test case (load in browser and press the Test button)

Observed on Windows XPsp2 and Mac OS 10.4.11 Intel.

In Firefox 3, a setTimeout() that is initiated before an alert() does not fire until after the alert window is closed.  Please see the attached HTML test case.

This is a change in behavior compared to Firefox 2 (where setTimeout() timers fire while modal alert windows are open).  I also see this problem with nsIPromptService initiated windows that are created by extension code.

Is this change in behavior expected?  Or is it an accidental regression?

Comment 1

[Jesse Ruderman]

I was under the impression that this was intentional.

Comment 2

[Kathleen :Brade]

Hi Jesse.  Can you explain why this behavior, setTimeout() blocked by modal dialogs, is intentional?  Is it due to a security issue?  Is there another bug I can reference?  Thanks!

Comment 3

[Boris Zbarsky [:bzbarsky]]

See bug 52209.

Comment 4

[Mark Smith [:mcs]]

Thanks for the pointer to bug 52209.   To help other extension developers, I added this issue to http://developer.mozilla.org/en/docs/Updating_extensions_for_Firefox_3#Other_changes (suggesting that people use nsITimer instead if they need timers that are NOT blocked by modal windows).

Resolving this bug as INVALID.