Mark Smith [:mcs] Reporter
	Description • 17 years ago

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?

	Jesse Ruderman
	Comment 1 • 17 years ago

I was under the impression that this was intentional.

	Kathleen :Brade
	Comment 2 • 17 years ago

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!

	Boris Zbarsky [:bzbarsky]
	Comment 3 • 16 years ago

See bug 52209.

	Mark Smith [:mcs] Reporter
	Comment 4 • 16 years ago

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.