I noticed that some of the menu items in message windows (in mail) are greyed out, until you right click on the message body. Steps to reproduce: 1. Start N6 (or mozilla). 2. Start your mail (login, etc....) 3. Double click on any message in your inbox. A separate window will open up with the message in it. You will notice that if you pull down the FILE menu, CLOSE, GET NEW MESSAGES, GET NEW MESSAGES FOR, GET NEXT 500 NEWS MESSAGES, and PRINT are all greyed out. There are others greyed out under the other menus, as well. To clear this: 1. Right click on the message body. This will bring up a context menu for the message. 2. Dismiss the menu by clicking anywhere outside the menu. You will now notice that the menu items that were previously greyed out are now selectable. I was able to reproduce this on mozilla build #2001052209 on both hpux 11.00 and 11i. I was NOT able to reproduce this on linux using the linux mozilla build #2001052210.

updating qa contact

adding blocker

I see it ... left clicking inside the message body works too

I'm seeing this problem also on Linux build 2001052208 and 2001052213, however Barrett's only seeing it on HPUX. Could someone else test this before I reassign it to Linux? Thanks!

Build 2001-05-21-08: Linux RH 6.2 I can reproduce the problem on linux so I think this is a general linux/unix problem. I also could not reproduce on win and mac. Additional menu items that appear effected are: - Edit|Select All - Search|Find in This Message - Go|Next submenus - Go|Previous submenus - Message|Reply - Message|Reply All - Messsage|Forward - Message|Edit Message as New

Thanks for testing this! Based on nbaca's comments I'm changing the OS to Linux (although it also happens on HPUX) and reassigning to mscott for mailnews attention.

seth is the owner of the front end.

Not an issue with linux 2001121300

Correction... just opened a draft message, and two menus where grayed out until I clicked in the message

examing with solaris nightly build 20020901. this bug does not exist at all suggesting to close it.

Agree with comment 10, this bug appears to be have been taken care of.