Closed
Bug 100492
Opened 23 years ago
Closed 14 years ago
modal error window doesn't de-iconify nor pop up to front
Categories
(SeaMonkey :: UI Design, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: b.lecomte, Assigned: jag+mozilla)
Details
when a modal alert (information, question or error) window arrives in an iconified parent-window, it doesn't de-iconify. (for example "the operation timed out when attempting to contact <hostname>", or "<hostname> wants to set a cookie, allows it ?") then, all netscape can be frozen, including the mailer, until the user finds the right window to close. Moreover, when the parent-window is raised, the dialog box stays behind. WorkAround: don't iconify "running" windows ! BugTraqID: 4503499
Comment 1•23 years ago
|
||
I think the solution is to make the dialogs not block other Mozilla windows. I don't like it when windows pop in front just to tell me "I couldn't connect to <hostname>".
Comment 2•23 years ago
|
||
what build are you testing?
Assignee: asa → pchen
Component: Browser-General → XP Apps
QA Contact: doronr → sairuh
Reporter | ||
Comment 3•23 years ago
|
||
SUNWns6 Mozilla/5.0 Netscape6/6.01
Reporter | ||
Comment 4•23 years ago
|
||
(X11; U; SunOS 5.8 sun4u; en-US; m18) Gecko/20010307
Updated•23 years ago
|
QA Contact: sairuh → jrgm
Comment 5•23 years ago
|
||
there is an existing bug about the dialogs being window-modal. This is just about deiconifying.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 6•23 years ago
|
||
In that case, I disagree with this bug :) I don't think modal dialogs should jump in front of anything but their parent window. IMO, the real problem here is bug 65521, "[linux] modal dialogs should only freeze parent window (not all windows)". By the way, Brice, you're using a very old version of Mozilla. You can get a newer milestone at http://www.mozilla.org/releases/, or you can download a nightly build from http://ftp.mozilla.org/pub/mozilla/nightly/latest/.
Reporter | ||
Comment 7•23 years ago
|
||
build ID:2001112114 go to http://www.boursorama.com when you log in, a security warning question box is opened. This box is a modal one and freeze all windows (included the mailer), but it's ok because you are working with its current parent window. what is not so good is : once you are log on such website, iconify this window. Enjoy yourself and open n other windows to surf around the world, there will be a time when all your windows will be frozen, just because the first one (iconified) has a modal question box asking about a security warning of unencrypted data that needs to be send to refresh the page. the game is now: you have less than 10s to find where is this box hidden. of course, I shouldn't have checked on the "Warn me before storing a cookie" nor the 5 SSL Warnings
Reporter | ||
Comment 8•23 years ago
|
||
*** This bug has been marked as a duplicate of 65521 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
This bug still partly exists on Solaris, CDE. Now modal dialogs only freeze parent window. But when you deiconify a window that has a modal dialog open, like "Open File...", the dialog box stays behind its parent window. Unless you find the dialog, the parent window is unresponsive. Very annoying on CDE.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 10•21 years ago
|
||
Reassigning bug to default owner
Assignee: paulkchen → jag
Status: REOPENED → NEW
QA Contact: jrgmorrison → pawyskoczka
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
Comment 11•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Comment 12•14 years ago
|
||
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago → 14 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•