108135 - Quit command key label disappears from Application menu

Status: VERIFIED INVALID

(SeaMonkey :: UI Design, defect)

Description

[Anthony Graham]

Command-Q label exists in two menus on Mac OS X: the Application menu (Mozilla)
and the File menu. This, in and of itself is a UI issue.

However, it's possible to cause the Command-Q label to disappear from one of the
menus.

To cause the Command-Q label to disappear from the Mozilla menu:

1. Launch Mozilla
2. Verify the Command-Q label exists under the Mozilla menu
3. Switch to another application
4. Switch back to Mozilla
5. Click a menu to the right (like the QA menu)
6. Now, without leaving the menu bar, slide the cursor over to the left over
each menu toward the Mozilla menu
7. When you hit the Mozilla menu, the Quit command exists, but its label
(Command-Q) is gone

This behavior exists in Mozilla 0.9.5, and is much easier to trigger in Netscape
6.2.

Tested on Mac OS X 10.1 build 5L14
PowerBook Titanium
Screen resolution 1152x768

Comment 1

[Chris Petersen]

Confirming issue with the Nov 1st build (2001-11-01-08)

Comment 2

[timeless]

.

Comment 3

[sairuh (rarely reading bugmail)]

->pink

Comment 4

[Mike Pinkerton (not reading bugmail)]

does this happen on the trunk? the file menu no longer has 'quit' in it there.
i'm guessing this has already been fixed.

Comment 5

[Chris Petersen]

Can't reproduce on the Mac OS X 10.1 Nov 6th trunk build. 

Tony, please try with a newer trunk build.

Comment 6

[Mike Pinkerton (not reading bugmail)]

reopen if it's still the case on the trunk.

Comment 7

[sairuh (rarely reading bugmail)]

mass verification of Invalid bugs: to find all bugspam pertaining to this,
set your search string to "MagaritaLuisaChascarilloAvoidsInvalidBugs".

if you think this particular bug is *still* an open issue, please make sure of
the following before reopening:

a. where relevant, do check that it's actually still a problem with ***recent
trunk builds*** on the all appropriate platform[s]

b. provide clear, compelling reasons why this bug should be considered a valid one.