329578 - Some fields (adddress/subject/body) disabled on compose mail [mail composition, mail editor]

Status: VERIFIED DUPLICATE of bug 307672

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Aaron Lawrence]

After running Seamonkey 1.0 for a while, I get to this situation: if I click reply to an email, then the window comes up with the subject and address fields filled in as expected, but disabled.

This only goes away after restarting the whole of the suite (closing the mail window is not enough).

I couldn't find an existing bug. This sounds similar but not identical to bug 129410; however that clearly can't be the same issue as it was in 2002.

Comment 1

[Aaron Lawrence]

Attachment: Compose window with subject+address disabled

Comment 2

[Aaron Lawrence]

Mail otherwise works fine for an interdeterminate amount of time. 
This was a new profile made for Seamonkey. I have reattached various mailboxes from a previous (Mozilla 1.7.x) version. They are quite large. Inbox is 600MB.
Not using local folders.

Comment 3

[Mike Cowperthwaite]

The screenshot may be a reply, but the To: field is not filled in.

Do you encounter this problem with replies?  Once you get into this situation again, try a new message window.  Also, try opening a second compose window (using Reply) while the first, broken one is still open -- does that second window show the same problem?

Do you have any extensions installed?

Fixing branch ID.

Comment 4

[Aaron Lawrence]

I have no extensions, it is a clean SeaMonkey 1.0 install.

You are right; in this case the To: is not filled in, but it is a reply as you can tell from the subject field.  Note: Replies could be irrelevant, it's just that it has only first happened on replies so far. Removed mention of reply from summary.

In a second recent incident, the new compose window came up with the fields not LOOKING disabled, but unable to be typed into.

Once this happens, the problem is permanent; I cannot compose new messages whether replies or not. New message windows all have the same problem. Closing the first one, or the whole mail window does not help.

Comment 5

[Aaron Lawrence]

OK, it's just happened again.
This time To: and Subject: are OK - are able to be edited.
However the body field cannot be typed into, and is blank (does not have the inline forward, or "Blah said: ..." quoted stuff.

Forward as Attachment shows a new window with an attachment.
Forward as inline shows nothing in the body field. 
Reply shows nothing in the body field.

So it appears to be some kind of random timing issue. Perhaps an exception causes initialisation of the new message window to be aborted or something.

Interestingly: closing this window always prompts "Message has not been sent. Do you want to save the message in the Drafts folder?" even though I haven't typed anything.

Comment 6

[Aaron Lawrence]

OK, first solid info, from Javascript console:

Error: [Exception... "Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIMsgCompose.initEditor]"  nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)"  location: "JS frame :: chrome://messenger/content/messengercompose/MsgComposeCommands.js :: InitEditor :: line 3200"  data: no]
Source File: chrome://messenger/content/messengercompose/MsgComposeCommands.js
Line: 3200

this occurs when I Compose New message, or a reply, or a forward.

When I close this window:

Error: gMsgCompose.editor has no properties
Source File: chrome://messenger/content/messengercompose/MsgComposeCommands.js
Line: 191

Just confirming version:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0

NEXT: When I composed another message with the first one open, the problem dissappeared. The new window was OK, and subsequent windows worked also.

THis is a laptop with Pentium M 2GHz.

Comment 7

[zug_treno]

(In reply to comment #6)
> Error: [Exception... "Component returned failure code: 0x80004003
<..>
> Source File: chrome://messenger/content/messengercompose/MsgComposeCommands.js
> Line: 3200

This seems to be the same error message as mentioned in bug 307672 comment 6 (also 11, 18 and 34), I guess this is a duplicate?

Comment 8

[Aaron Lawrence]

Yes, thanks.

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