Closed
Bug 231521
Opened 22 years ago
Closed 21 years ago
In <chrome://messenger/content/mailWindowOverlay.js>, JavaScript "Error/Exception ... NS_ERROR_INVALID_POINTER ... nsIMsgMailNewsUrl.mimeHeaders ... HandleMDNResponse"
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 249195
People
(Reporter: sgautherie, Assigned: sspitzer)
Details
Attachments
(2 files)
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6) Gecko/20040113] (W98SE)
{
Error: [Exception... "Component returned failure code: 0x80004003
(NS_ERROR_INVALID_POINTER) [nsIMsgMailNewsUrl.mimeHeaders]" nsresult:
"0x80004003 (NS_ERROR_INVALID_POINTER)" location: "JS frame ::
chrome://messenger/content/mailWindowOverlay.js :: HandleMDNResponse :: line
2118" data: no]
Source File: chrome://messenger/content/mailWindowOverlay.js
Line: 2118
}
How it happened:
The focus was on a message in the thread pane;
I get some more emails;
I sorted from date(!?) to thread;
This created a thread for the focused message.
So far, so good; now what went wrong:
The thread looked like 5 messages long,
but there were 3 actual messages only,
which I deleted one by one,
when the 4th, then 5th, "messages" were displayed, I got this exception one time
for each.
The thread was the last of the pane, if that matters.
I did not try to interact further with them:
I focused another message, resorted the pane;
display was now as expected.
| Reporter | ||
Comment 1•22 years ago
|
||
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6) Gecko/20040113] (W98SE)
It happened again, +/- same case;
but, this time, the thread is not the last in the pane.
| Reporter | ||
Comment 2•22 years ago
|
||
This is when I get the exception !
Comment 3•21 years ago
|
||
*** This bug has been marked as a duplicate of 249195 ***
Status: NEW → RESOLVED
Closed: 21 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
•