366698 - News-Reply: Message Composition Window's Text and Subject locked for ever

Status: RESOLVED DUPLICATE of bug 307672

(SeaMonkey :: MailNews: Message Display, defect)

Description

[R.K.]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.9) Gecko/20061211 SeaMonkey/1.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.9) Gecko/20061211 SeaMonkey/1.0.7

Occasionally (after ~15 Replies or some hours of using SeaMonkey):
Upon Reply-Botton in News the Message Composition Window's Text and Subject is locked. The subject field shows the subject in grey and is locked and the text child window is totally empty and locked - you cannot put the cursor or type in anything. 

This behavior will then be for ever the same, unless one closes all SeaMonkey Windows (incl. Browser Windows) - the SeaMonkey icon in task bar then seems to be renewed and SeaMonkey be reloaded somehow (or full exit & restart of SeaMonkey) - only then the bug status disapears and one can use the News-Client again for some time until it happens again.

I see this since SeaMonkey 1.0 on all my Computers and hoped for a bug-fix every update :-) -  1.0.7 again didn't solve it, so I write now. But guess almost any frequent news client user faces this need for SeaMonkey reboots. I don't use ThunderBird (probably a software for low frequency News users) enough to see if the bug is also there. 


Reproducible: Sometimes

Steps to Reproduce:
1. use SeaMonkey News Reader and News-Reply/Composer a while
2. with some probability or after a "use-count" or so this bug status is achieved
3. the problem will not disapear until SeaMonkey is reloaded.

Comment 1

[Mike Cowperthwaite]

Looks like another dupe of bug 307672.

Comment 2

[R.K.]

I find these errors in the JS console after this bug:


Error: Unknown namespace prefix 'html'.  Ruleset ignored due to bad selector.
Source File: chrome://messenger/skin/messageBody.css
Line: 54


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


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


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


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


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

Error: this.mCurrentBrowser has no properties
Source File: chrome://global/content/bindings/tabbrowser.xml
Line: 0

---



And once the bug manifested in another way: though accounts are configured, upon Reply(to News) SeaMonkey raised the dialog to create a news account (Name, email address etc.) saying that there is not a configured account. While that config dialog was open, the mail composer windows was in background showing empty fields. Then when I canceld the config dialog, the mail composer windows was filled with pre-existing config data and continued normally. Just I've there is some time lag until he knows about the config data. Don't know if this is another bug, it was there only once.

Comment 3

[Mike Cowperthwaite]

(In reply to comment #2)
> I find these errors in the JS console after this bug:

Yeah -- with those errors, this is definitely a dupe.


> And once the bug manifested in another way: though accounts are configured,
> upon Reply(to News) SeaMonkey raised the dialog to create a news account
> [...] saying that there is not a configured account. 

I've seen that occasionally myself.

> Don't know if this is another bug, it was there only once.

I would say it is another bug, but the bug is with the account wizard popping up for no reason!

Thanks.