Closed Bug 727399 Opened 14 years ago Closed 14 years ago

when two tabs display a modal dialog, and they're closed FIFO, the first tab shouldn't resume until the modal dialog from the second tab is closed

Categories

(Firefox :: Untriaged, defect)

Product:
Firefox
Component:
Untriaged
Version:
12 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: jochen, Unassigned)

Details

When you open two tabs that both show an e.g. alert(), and you close the dialogs in FIFO order, the alert() in the first tab should only return after the alert() in the second tab returned. With the tab-modal implementation, the first alert() returns immediately.
I'm not sure I understand this correctly. If I have let's say 100 tabs open, and there are alerts in 7 of them, shouldn't I be able to continue working in my current tab before I have localized all alerts, found out in which order they have been opened and then closed all alerts that have been issued before the one in the current tab?
I agree that having the ability to work in whatever tab you chose is desirable. This bug is just pointing out that the spec'd behavior is different - alert() should block the whole browser. Again, I'm not saying that it's desirable, but it's a change in behavior the way it's implemented now.
(In reply to Jochen Eisinger from comment #2) > I agree that having the ability to work in whatever tab you chose is > desirable. This bug is just pointing out that the spec'd behavior is > different - alert() should block the whole browser. According to which specification?
https://developer.mozilla.org/en/DOM/window.alert says "Dialog boxes are modal windows - they prevent the user from accessing the rest of the program's interface until the dialog box is closed." I read that as "program" being the "browser", and it's how it used to be implemented in Firefox as well.
ok, seems like it got this all wrong. The actual behavior of Firefox is that the first tab won't return from it's alert() until the second does. So I'll close this bug, and file a new one to track this.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.