Closed
Bug 210159
Opened 21 years ago
Closed 15 years ago
In <chrome://messenger/content/messageWindow.js>, JavaScript error "Exception ... NS_ERROR_FAILURE ... nsIMsgMessageService.messageURIToMsgHdr ... extractMsgKeyFromURI"
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: sgautherie, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.4) Gecko/20030612 Build Identifier: Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.4) Gecko/20030612 (I chose the MWFE component based on the js filename: feel free to select a more appropriate component.) (This is v1.4rc2.) Reproducible: Didn't try Steps to Reproduce: (I am not sure of what triggered this error.) Actual Results: I found 2 of these, one right after the other (in the JS Console) [ Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgMessageService.messageURIToMsgHdr]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://messenger/content/messageWindow.js :: extractMsgKeyFromURI :: line 396" data: no] Source File: chrome://messenger/content/messageWindow.js Line: 396 ] (I guess that it happened while I was "playing" on bug 206278 and bug 209899, but I couldn't get another error when I tried to "replay" what I could have done...)
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•19 years ago
|
Assignee: sspitzer → mail
Reporter | ||
Updated•16 years ago
|
Assignee: mail → nobody
QA Contact: esther → message-display
Suite 1.4 is long gone and Win95 is EOLed. SeaMonkey trunk doesn't work on win95 either. Reporter (sgautherie), can you try and reproduce with SeaMonkey v2.0a2 or 2.0a3pre running on a minimum of Win2k.? (2.0a3 and 2.0b1pre versions aren't stable enough for everyone's daily use yet).
Reporter | ||
Comment 3•15 years ago
|
||
After all this time, it looks like it was a one-timer (with no steps to reproduce). R.Incomplete *** Fwiw, called function name has changed: { 406 function extractMsgKeyFromURI() 407 { 408 var msgKey = -1; 409 var msgHdr = messenger.msgHdrFromURI(gCurrentMessageUri); 410 if (msgHdr) 411 msgKey = msgHdr.messageKey; 412 return msgKey; 413 } }
Severity: major → normal
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•