12480 - [PP] compose menus are missing after composing 1st msg that contains an attachment

Status: VERIFIED DUPLICATE of bug 12335

(MailNews Core :: Composition, defect, P3)

Description

[pmock]

Build Date & Platform Bug Found:
 MacOS seamonkey build 1999-08-24-11-m9 installed on PPC 9600/300 OS 8.5.1

Overview Description:
 Apprunner fails to draw the message compose menus on the second compose window
you open up after attaching an file attachment on the first message.  The only
menu displayed is the "Help" menu.  If you try to access the help menu, the
application crashes.

Steps to Reproduce:
1) Start Apprunner
2) Open Messenger
3) Start a new message
   I was using a HTML compose window
4) Address the message to yourself
5) Add a subject title
6) Type a short message in the message body
7) Select the File menu and select attach->web page or attach-> file
8) Type in a web page url or select a file then click OK
9) (optional) Send the message.
   It does not matter if you send the message or not.  The first message is sent
10) Start a new message
    Notice that only the help menu is available
11) Select the help menu
    Apprunner crashes

Actual Results:
 The 2nd compose windows renders except for the menus.  You can send messages
with this compose window but you can not access any of the menus.  If you select
the "Help" menu, the application crashes.

Expected Results:
 The compose window should display all menus and should not crash.

Additional Builds and Platforms Tested On:
 This problem does not occur on Win32 or Linux.  I tried the following builds:
  Win32 seamonkey build 1999-08-24-13-m9
  Linux seamonkey build 1999-08-24-11-m9

Additional Information:
 The attach button on the compose toolbar is still functional.  I can attach
files but without the File menu, I can not access the other attachment options.

Comment 1

[Jean-Francois Ducarroz]

another scenario for the menu bug. same as bug 12335


*** This bug has been marked as a duplicate of 12335 ***

Comment 2

[lchiang]

I've gone ahead and raised the othe bug to a blocker status.