Closed
Bug 316179
Opened 19 years ago
Closed 19 years ago
message composition window grayed-out
Categories
(MailNews Core :: Composition, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 307672
People
(Reporter: eyalroz1, Unassigned)
Details
(Keywords: qawanted)
With recent nightlies, sometimes I get to a situation in which when I open a message compose window, the fields are grayed-out and I can't enter any text. I can't consistently reproduce this, but it's happened to me a lot. Restarting mozilla fixes the problem; sometimes closing all open composition windows and/or switching composition from text to HTML or vice-versa fixes the problem.
Comment 1•19 years ago
|
||
(In reply to comment #0)
> Restarting mozilla fixes the problem; sometimes closing all open
> composition windows and/or switching composition from text to HTML or
> vice-versa fixes the problem.
Having the problem fixed by "switching from text to HTML" implies a cached-composition-window problem. Next time you see it, try following it up by immediatley opening *another* composition window.
I assume these are trunk builds (1.6a1). Do you have any extensions installed that might be causing this?
Reporter | ||
Comment 2•19 years ago
|
||
(In reply to comment #1)
> I assume these are trunk builds (1.6a1). Do you have any extensions installed
> that might be causing this?
>
Maybe... BiDi Mail UI. Mozilla gives me hell whenever I install a nightly - fscking up the chrome until I remove and reinstall the extension. Also, there's
https://bugzilla.mozilla.org/show_bug.cgi?id=311963
But all this is probably unrelated to the graying-out thing. Haven't been able to reproduce it again (although recent nightlies are otherwise flakey).
Reporter | ||
Comment 3•19 years ago
|
||
Seeing it again just now, with sm 2005-11-27. JS console says:
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 3187" data: no]
Source File: chrome://messenger/content/messengercompose/MsgComposeCommands.js
Line: 3187
Error: gMsgCompose.editor has no properties
Source File: chrome://messenger/content/messengercompose/MsgComposeCommands.js
Line: 192
Still not sure how to reproduce this. This time I was composing HTML e-mail (don't ask why).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 4•19 years ago
|
||
*** This bug has been marked as a duplicate of 307672 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Updated•18 years ago
|
Status: RESOLVED → VERIFIED
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•