User-Agent: Mozilla/3.01Gold (Macintosh; I; 68K) Build Identifier: An application started a mozilla browser to preview something. I then pressed the 'file->quit' menu entry only to find out later that this also closed the mozilla I still had running on another virtual desktop (replace this with iconified or obscured if you're not a unix user). I had to create a new password for a site I was trying to download something from!! Very annoying! Quit should only quit the mozilla that was automatically started from my other application. It should leave all other stuff alone! Reproducible: Always Steps to Reproduce:

The application connected to the existing Mozilla process and asked it to open another window. At no point were there multiple processes running, and this window is in no way special. So when you select "quit", you quit the Mozilla process... all of it. This is why the "close" option exists.

Finding close at the top of the file menu is really strange; in just about all other applications I have here I looked and found it grouped with 'quit' (or exit, which seems to be the same). What you say about the process may be true; but I have to take your word for it. Not that I don't trust you, its that this is in no way obvious to me. I have absolutely no use for closing all open windows of mozilla. I mean; how often do you want to clean up _all_ your mozilla windows? I suggest to rename 'quit' to 'close all windows', since the quit is about a unix-process. And implementation details should not be something the user has to know. Renaming it to 'close all windows' takes away any doubts to the meaning of the function.

Bug 65121 is about this problem. *** This bug has been marked as a duplicate of 65121 ***