Closed Bug 304287 Opened 19 years ago Closed 19 years ago

Switching between news folders fails: GetMessagePaneFrame().location has no properties

Categories

(SeaMonkey :: MailNews: Message Display, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: philip.chee, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050810 SeaMonkey/1.0a Mnenhy/0.7.2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050810 SeaMonkey/1.0a Mnenhy/0.7.2.0

This is similar to Bug 282593 but for news folders. The fix for Bug 282938 does
not seem to make this variation go away. The specific javascript error message is:

Error: [JavaScript Error: "GetMessagePaneFrame().location has no properties"
{file: "chrome://messenger/content/msgMail3PaneWindow.js" line: 1131}]
Source File: chrome://messenger/content/msgMail3PaneWindow.js
Line: 1131

Reproducible: Always

Steps to Reproduce:
1. Open mailnews
2. Click on one news folder
3. Click on another news folder

Actual Results:  
The list of articles/messages does not change to reflect the contents of the
selected newsgroup.

Expected Results:  
The list of articles/messages should change to reflect the contents of the
selected newsgroup

I have to click on another random newsgroup and then click back on the one I
want to read to force the message list to refresh.
Further info: I have the preview pane dragged all the way down so that it is
hidden. If I drag the grippy up slightly so that the preview is just visible,
this problem does not occur. QA probably did not test for this edge case before
closing the original bug.
Summary: witching between news folders fails: GetMessagePaneFrame().location has no properties → Switching between news folders fails: GetMessagePaneFrame().location has no properties
Seems to me this is a bug in Mnenhy, since I'm running build 2005-08-11-06 on
Windows XP SeaMonkey trunk without any problems whatsoever.

Even your scenario in comment 1 works for me.

Have you contacted/filed a bug with the folks here:

http://mozdev.org/bugs/buglist.cgi?product=mnenhy&order=Bug+Number ?
Version: unspecified → Trunk
I confirm that disabling Mnenhy makes this problem go away. Marking as INVALID.
I'll notify the Mnenhy folks.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.