37537 - New Navigator Window on File menu twice

Status: VERIFIED WONTFIX

(SeaMonkey :: UI Design, defect, P4)

Description

[Blake Ross]

Build ID: 2000042808

Is it necessary to have File | New Navigator Window  AND File | New | Navigator 
Window, both of which do the exact same thing and use Ctrl+N?

One's gotta go...

Comment 1

[sairuh (rarely reading bugmail)]

i could go either way on this. assigning to german to make the call. btw, this
is an XPApps bug, not XPMenus :-), since it deals with the applications attached
to a menu (not the lowlevel menu behavior itself).

Comment 2

[shuang (gone)]

set to M18 for later call.

Comment 3

[Blake Ross]

german, any word on this? having this on the menu twice makes us look pretty 
silly.  IIRC, the spec was to have the first item on the File menu be 
the "default" or most commonly used "New" item, which in this case _would_ 
be "New Navigator Window"   This is also what we've done in the Manage 
Bookmarks window (File | New Bookmark, or File | New > submenu for less 
commonly used commands).  Thus, I propose we remove the New Navigator Window 
command from the File | New > submenu to follow the spec and ensure consistency.

Although, this is somewhat odd UI menu design, to have an independent, 
standalone New command and then, right below it, a whole New > submenu that 
encompasses other "New xxx" commands.  Traditional UI design, on win32 at 
least, would designate that New Navigator Window belong in the New > submenu 
with everything else (and as IE has it)...

welp..there's both sides of the argument.  What do you all think?

Comment 4

[Blake Ross]

Reassigning to myself since this is an extremely easy bug to fix, but nothing's 
happening on it.  Since there's been no word of which way we should go, for now 
I'm going to remove the Navigator Window item in the File | New > submenu, 
since (iirc) the first item on the New menu was to be the default or most 
commonly used New item, thus making it more accessible (as I said earlier).

Comment 5

[Blake Ross]

Attachment: patch - removes Navigator Window from File | New > submenu

Comment 6

[Blake Ross]

I'm ready to check this in and just need approval that this is what we want to 
do (remove it from the submenu) ...don? german?

Comment 7

[timeless]

I object based on the spec, new navigator window is supposed to always be on 
the menu. For the navigator window there are no component specific items, just 
app global items, which make the user feel comfortable w/ the menus.

Feel free to file a bug against moz for having new blank page to edit below the 
app global separation.
removing patch; marking invalid; I can't reassign it :(

Comment 8

[don]

I'm re-opening this bug.  Having the commands in the same menu twice is just 
silly.  We need to rethink this.

Comment 9

[Matthew T (active 1999-2002)]

Yes, and the spec also contains such gems as `Exit will become Quit' and a 
`Tasks' > `Go To Window' submenu, so I don't think we can take it too seriously.

If you removed `Navigator Window' from the `New' submenu, you would still have 
the problem that there were two `New' items in the root menu, so `Open' would 
still be further down than users were instinctively expecting it to be. So my 
vote would be to ditch the initial default menu item, and just have the submenu.

Comment 10

[Matthew T (active 1999-2002)]

Whether this gets changed depends on the resolution (either FIXED or WONTFIX) of 

bug 63133.

Comment 11

[Blake Ross]

back to Ben for now...

Comment 12

[Jesse Ruderman]

*** Bug 113776 has been marked as a duplicate of this bug. ***

Comment 13

[timeless]

per comment 10

Comment 14

[sairuh (rarely reading bugmail)]

v

Comment 15

[Jesse Ruderman]

*** Bug 121767 has been marked as a duplicate of this bug. ***