Closed
Bug 178844
Opened 23 years ago
Closed 22 years ago
Open message in new window displays empty "Mail & Newsgroups" window
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 106461
People
(Reporter: weymar, Assigned: sspitzer)
References
Details
C.f. Bug# 125306
I have been seeing the same problem since mid-December builds. When I see my
newsgroup message or a mail message, I want to open it in a new window that has
the message all by itself - not the 3 pane layout. This has always worked until
mid-December builds. I keep thinking the problem will go away with a later
build, but even with 1.3b 20030123, the problem persists.
NOTE: I am running this on Windows 98 -- note Windows XP where the original bug
was opened.
*** Bug 192161 has been marked as a duplicate of this bug. ***
*** Bug 193307 has been marked as a duplicate of this bug. ***
*** Bug 193570 has been marked as a duplicate of this bug. ***
Those who see this bug (Matthew Weymar, Norbert Zimmermann, Matthias)
Can you try something, and add comment here:
1: Open tools->Web Development->Javascript Console, then hit the "Clear" button
in it, to get rid of possibly old output
2: Then try to reproduce the bug (in other words open a message in a new window)
Is there any output? If yes: Please copy it, entry by entry, and paste into this
bug-report.
| Reporter | ||
Comment 6•23 years ago
|
||
I can now open messages in a new window. No "output" in the JavaScript Console
if that's what you were asking about.
Still, this shouldn't be nec., should it? To clear the JavaScript Console in
this way?...
This is what i get :
---
Error: uncaught exception: [Exception... "Component returned failure code:
0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]" nsresult:
"0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)" location: "JS frame ::
chrome://messenger/content/msgHdrViewOverlay.js :: <TOP_LEVEL> :: line 61"
data: no]
Error: redeclaration of const MSG_FOLDER_FLAG_TRASH
Source File: chrome://messenger/content/commandglue.js
Line: 1
Error: gCollapsedHeaderView has no properties
Source File: chrome://messenger/content/msgHdrViewOverlay.js
Line: 171
---
Matthias
I got the same error list:
----
Error: uncaught exception: [Exception... "Component returned failure code:
0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]" nsresult:
"0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)" location: "JS frame ::
chrome://messenger/content/msgHdrViewOverlay.js :: <TOP_LEVEL> :: line 61"
data: no]
Error: redeclaration of const MSG_FOLDER_FLAG_TRASH
Source File: chrome://messenger/content/commandglue.js
Line: 1
Error: gCollapsedHeaderView has no properties
Source File: chrome://messenger/content/msgHdrViewOverlay.js
Line: 171
----
Norbert
Comment 9•23 years ago
|
||
*** Bug 193570 has been marked as a duplicate of this bug. ***
Comment 10•23 years ago
|
||
Resolving as new, based on the duplicates
Status: UNCONFIRMED → NEW
Ever confirmed: true
| Reporter | ||
Comment 11•23 years ago
|
||
Sorry for the confusion, but "I swear" clearing the JavaScript Console *did*
solve the problem - at least temporarily, or for certain types of msgs.
Nevertheless, I am still having the same problem - w/ exactly the same results
as those reported by Matthias & NZ.
Comment 12•23 years ago
|
||
I have the same problem.
I have Windows 2000 with Mozilla 1.2.1
This as the messages in javascript console :
Error: uncaught exception: [Exception... "Component returned failure code:
0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]" nsresult:
"0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)" location: "JS frame ::
chrome://messenger/content/msgHdrViewOverlay.js :: <TOP_LEVEL> :: line 64"
data: no]
Error: gCollapsedHeaderView has no properties
Source File: chrome://messenger/content/msgHdrViewOverlay.js
Line: 174
Comment 13•23 years ago
|
||
ditto as to what the other's said. I got the very same three JavaScript error
messages. Windows 98 here.
Comment 14•23 years ago
|
||
I get the JS errors from message #12. Looking at the source shows this is a
problem with the collected addresses (nsIAbAddressCollector). When I open the
preferences window and try to tell Mozilla to collect email addresses and click
OK, the whole of mozilla crashes with an error in addrbook.dll. I tried erasing
history.mab, which got recreated but didn't solve the problem. I tried editing
prefs.js to tell mozilla to collect addresses (although I don't really want to),
but mozilla reset the preferences on startup and still didn't work.
This is on Windows 98, mozilla 1.2.1
Comment 15•23 years ago
|
||
I found the reason this bug was occurring was because abook.mab was corrupt. I
managed to repeat the error on Win2k and Mozilla 1.3b. Once I replaced
abook.mab with a non-corrupt address book, everything started working properly.
I noticed another side effect of having a corrupt address book was that messages
weren't displaying with nice headers - the headers were showing in a box in the
html window instead.
(I think Mozilla needs to have a lot better error checking for corrupt files, as
this seems to be (in my experience) the most common cause of crashses).
Comment 16•23 years ago
|
||
true - replaced abook.mab , messages open correctly again
Comment 17•23 years ago
|
||
Replacing abook.mab in my W2K-1.3beta setup with a newly created one (using
address book - file - new - address book) did resolve the bug for me as well.
The newly created address book was named by the system abook-1.mab. Renaming it
to abook.mab brought back the email display.
@James Ots: Thank you very much for finding and communicating the solution to
this bug.
- Norbert -
Comment 18•23 years ago
|
||
well, that is certainly an interesting fix. but it works! i unloaded the
address book, closed moz, reopened it (creates a new, blank file) and imported
everything back.
now can someone explain to me why a corrupt address book causes the display to
go gaflooey?
Comment 19•23 years ago
|
||
I think the reason is that when you open an email it tries to open the address
book for some reason, and when it can't then it gives up and doesn't do
anything. While the preview window is slightly more robust and just shows the
message slightly differently when the address book is corrupt.
Of course, what it should do is tell you the book is corrupt and then try to fix
it, or create a new empty book, rather than just messing up. (I'd offer to write
it, but I don't understand the source code well enough yet).
Comment 20•23 years ago
|
||
deleteing all my address.mab fixed it for me too. It also made it so I could
also get to attachments in emails. I'll have to find that bug number to make
that comment there. Another thing I don't understand about this issue is why
did the address book get corrupted by those of us who got this bug. I never
even use the address book.
Comment 21•23 years ago
|
||
Comment 22•23 years ago
|
||
I meant bug 106461, not 106561
Comment 23•22 years ago
|
||
*** This bug has been marked as a duplicate of 106461 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•