211767 - when collapsing thread, the last 2 posts remain on screen and duplicate with every more expand/collapse

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[mbirth]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624

While reading posts of a long thread and then collapsing the thread, there were
the 2 most bottom posts remaining in the list. After expanding again, I had the
complete list of posts plus the 2 dupes. After collapsing again, there now were
4 posts: twice the 2 most bottom posts. With every expand/collapse, there were 2
more dupes added to the list. After switching to another group and back again,
the list was clean again but when expanding/collapsing threads with more than 5
messages, the problem occured again.

Reproducible: Couldn't Reproduce

Steps to Reproduce:
1. 
2.
3.

Actual Results:  
2 posts left on screen although the thread was collapsed.

Expected Results:  
Only the initial post of the thread should be visible.

Comment 1

[Rob North]

I'm seeing this on Windows XP, Moz 1.8a3 (2004081709).

It's extremely repeatable on certain threads, but need to check wether behaviour
persists across sessions.

I beleive I've seen this on Linux.
Will confirm that this is present on Linux.

Comment 2

[Rob North]

On XP, this problem does persist across sessions.

The thread that causes problems is:

in newsgroup: netscape.public.mozilla.seamonkey.
Thread name: Accessing Talkback Data

I'd like to look in the .msf file for clues to this problem,
but don't know where to start. Suggestions anyone?

Comment 3

[Rob North]

This bug also occurs in Linux, on the same usenet thread.
(Note that I share my mail and news accounts between Windows & Linux)

Comment 4

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.