80553 - Move Close away from save as and near open.

Status: RESOLVED WONTFIX

(SeaMonkey :: UI Design, enhancement)

Description

[timeless]

from bug 65121 {windows only}
------- Additional Comments From [e-mail]  2001-05-13 00:46 -------
If Close can't be put down with Exit, I think it should be put above the
separator, at the bottom of section that contains New and Open, not together
with Save As.

Putting it at the bottom of the section would be a little bit more noticeable 
since user would expect it to be "at the bottom".

That is the way it is done in MS Word 2000 - another example of SDI application
that has both Close and Exit in it's File menu.

Comment 1

[Matthew T (active 1999-2002)]

Microsoft doesn't have UI guidelines about where to put the `Close' item, 
except that they say to put it at the bottom if you don't have an `Exit' item 
(which is what bug 65121 is about).

Apple does have UI guidelines about where to put the `Close' item, and they say 
to put it exactly where we're putting it now.

Comment 2

[Alexey Chernyak]

We are talking Windows here, not Mac.

Under Windows, the current position of Close is totally awkward.
I think it's either should be moved where it is placed in the Microsoft
applications - away from Save, over to New and Open.
OR
Put it right above Exit - just like in Netscape 4.

I think latter is the best choice because:
1. More intuitive to user.
2. IE users won't be making the mistake of quitting whole app, when they want to
close just one window, and won't be losing data.
3. It is familiar to Netscape users. It is what they are used to and what they
expect.

We are talking Windows here.
Even if Microsoft doesn't have any guidelines about this, I think we should do
what is best for user comfort on this platform, not what is a guideline on
another platform.

Comment 3

[Zach Lipton [:zach]]

However, on mac, we should keep it where it is and NOT violate any 
guidelines.

Comment 4

[Alexey Chernyak]

adding keywords: pp, 4xp, dataloss

Comment 5

[timeless]

uid is being phased out.

Comment 6

[Blake Ross]

Reassigning obsolete bugs to their respective Seamonkey owners (i.e. nobody). 
If you want this fixed for Firefox, change the Product and Component accordingly
and reassign back to me.

Comment 7

[Serge Gautherie (:sgautherie)]

Filter "spam" on "guifeatures-nobody-20080610".

Comment 8

[:Hb]

this is not a dataloss bug. WONTFIX.