148040 - "Get Msgs", "Mark Newsgroup Read" fails (context menu)

Status: VERIFIED DUPLICATE of bug 147997

(SeaMonkey :: MailNews: Message Display, defect)

Description

[R.K.Aa.]

Current CVS, Linux

The context menu in mailnews suffer some hickups:

-right click newsgroup in folderpane
-mark newsgroup read

Result: nothing happens

Error: folderArray.AppendElement is not a function
Source File: chrome://messenger/content/mailCommands.js
Line: 386

--

Select properties: Properties sheet appears - along with this warning:

Error: uncaught exception: [Exception... "Component returned failure code:
0x80004002 (NS_NOINTERFACE) [nsISupports.QueryInterface]"  nsresult: "0x80004002
(NS_NOINTERFACE)"  location: "JS frame ::
chrome://messenger/content/folderProps.js :: hideShowControls :: line 229" 
data: no]

--

Fallout from bug 147448?

Comment 1

[R.K.Aa.]

starting to wonder if this is local horkage. I can't "Get msgs" either:
Error: folderArray.AppendElement is not a function
Source File: chrome://messenger/content/mailCommands.js
Line: 65

Comment 2

[R.K.Aa.]

Get Msgs fails untill i start composing a message.
Then 10 mails suddenly arrived, likely because of mailnews being set to
check/get mail every 5th minute.

However: for each mail that arrived, a new error spawned in JS console:

Error: uncaught exception: [Exception... "Component returned failure code:
0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIListBoxObject.getItemAtIndex]" 
nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame ::
chrome://global/content/bindings/listbox.xml#listbox.getItemAtIndex() ::
getItemAtIndex :: line 1"  data: no]

Now testing with trunk 2002052921, Linux

Comment 3

[R.K.Aa.]

pulled and rebuilt - all works fine again.
Resolving as dup of bug 147997 since the backout there fixed this.

(warnings when message arrive remains, but is something else. Doesn't hamper
functionality.)

*** This bug has been marked as a duplicate of 147997 ***

Comment 4

[[e-mail] (gone - use [e-mail] instead)]

verified dup