196850 - QuickLaunch is closing EVERY Mozilla window when I click Ok in information message window

Status: RESOLVED WONTFIX

Description

[Khimenko Victor]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130

If you click Ok in dialog "QuickLaunch is active, so Mozilla remains in memory
and can be started again quickly. To completely exit, right-click on Mozilla
icon in system tray and select Exit Mozilla" it'll close ALL Mozilla windows -
even windows opened in new session!

Reproducible: Always

Steps to Reproduce:
1. Start Mozilla with QuickLaunch active
2. Close Mozilla window
3. Dialog appears "QuickLaunch is active, so Mozilla remains in memory and can
be started again quickly. To completely exit, right-click on Mozilla icon in
system tray and select Exit Mozilla". DO NOT CLICK OK!
4. Start Mozilla again - you can use it as usual, open few windows, etc, but...
5. Go to still opened Dialog "QuickLaunch is active..." and press "Ok" there.
6. All Mozilla windows, dialogs and so on are closed. Oops.

Actual Results:  
All windows were closed, not just information dialog.

Expected Results:  
Close dialog and leave me with all other windows available OR may be close
dialog when I started it again but NOT close all windows I've not finished reading!

Comment 1

[Bruno 'Aqualon' Escherl]

confirming for Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3)
Gecko/20030310

Comment 2

[Chris Lyon]

->Quicklaunch

Comment 3

[Grace Bush]

what triggers the dialog..."QuickLaunch is active, so Mozilla remains in memory
and can be started again quickly. To completely exit, right-click on Mozilla
icon in system tray and select Exit Mozilla" is a file/exit. 

closing one or more windows using [x] in upper right corner  will not close all
mozilla windows nor trigger the dialog and allow you to continue working/reading

this is working as designed. 
see http://www.mozilla.org/xpapps/QuickLaunch/

Comment 4

[Khimenko Victor]

I do not complain about when dialog is SHOWN. It's working as designed: if
file/exit is selected or when last window is closed.

What DOES NOT work as designed is CLOSING this dialog when NEW BROWSING SESSION
is started.

I mean: it's normal dialog, it's not system modal, you are not forced to close
it to continue - you can just switch to other program. But if you leave this
dialog hanging around and start new browsing session you can not just close it:
if you'll do it you'll close all browser windows - and it's hardly expected result.

Comment 5

[Grace Bush]

I disagree, closing that dialog gives permission to close all open windows used
by that mozilla process.  If you don't want to close down, don't file/exit.  use
context menu to open other windows or use tabs to open other window

Comment 6

[Khimenko Victor]

The problem is that I *DID* *NOT* use file/exit.

Yes, sure, I once upon time used file/exit if this dialog is lurking round. 

But this can be easily few days ago (it was in my case - of course all this time
computer was hibernated, but it's another story).

Then, when I had 10+ opened Mozilla windows (with few tabs in each and new
message with unfinished letter) I stumbled upon this dialog and closed it.

Oops: all my windows with all my tabs and so on are gone too! Why ? To punish me
for not closing dialog in time ? I *DID* *NOT* wanted to quit yet!!! I just
closed some forgotten dialog from few days ago! And it closed EVERYTHING
including letter I typed at the time !

Disaster ? No - I can retype my letters usually. Annoying ? Yes. Very. I retyped
letter but I was not happy camper.

Comment 7

[Boris Zbarsky [:bzbarsky, bz on IRC]]

Confirming.  This is serious dataloss -- windows opened after that dialog comes
up should absolutely not be closed by the dialog.

Grace, is there a real developer this could be assigned to?

Comment 8

[Grace Bush]

Boris, 

ssu may be handling QuickLaunch issues these days.

I still believe it is working as designed- once you ask for file/exit, and ask
for that dialog to be displayed (it can be turned off and then NO warning is
given) - the application closes.  
this may be an enhancement request but not a bug

Comment 9

[Khimenko Victor]

If it's working as designed then it's bug in design.

It's a bug. How exactly is should be fixed - good question, there are many ways.
But as it's now it's a bug. With a potential for dataloss.

For example: when you select file/exit and have unsent letter Mozilla asks you
"Message has not been sent. Do you want to save the message in the Drafts
floder?" and you have three choices. When you are doing it in the way described
in my first message Mozilla will SILENTLY close window with unsent message. No
question, no choice, nothing. Window is closed and letter is lost. Composer
window with unsaved page is closed without questions and unsaved page is lost.

Mozilla (and any sane program) should NOT silently close windows with unsaved
data EVEN if user asked for file/exit - it should ask user to save it first.

Once again: I'm NOT complaining about windows opened BEFORE dialog is shown. I'm
complaining about windows opened AFTER dialog is shown. They ALSO are closed
SILENTLY. No confirmations, nothing. Windows are closed and data is lost forever.

Comment 10

[Matthias Versen [:Matti]]

Quicklaunch/Turbo Mode is no longer supported in Seamonkey 2 and Seamonkey1.X is in the maintenance mode (fixing only security bugs)