Closed
Bug 152584
Opened 23 years ago
Closed 23 years ago
Thread toggle changes position while reading messages; then unable to collapse thread
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 123858
People
(Reporter: s.vanslyck, Assigned: sspitzer)
Details
Attachments
(2 files)
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530
BuildID: 2002053012
See the attached pictures. While reading a newsgroup message thread, the thread
display toggle triangle button will reverse position to the "collapsed" state,
but not collapse the thread. Clicking the thread will then re-expand the thread,
from its already non-collapsed view, now showing each message twice. The error
stays in this state until the user moves to another newsgroup.
Reproducible: Sometimes
Steps to Reproduce:
I am not sure exactly how to reproduce this problem. It either occurs
intermittently or due to something happening which I've not been able yet to
zero in on. Today it happened while I was reading a newsgroup message, but I'm
not sure exactly when.
See attachments.
Reporter | ||
Comment 1•23 years ago
|
||
Reporter | ||
Comment 2•23 years ago
|
||
Reporter | ||
Updated•23 years ago
|
Summary: Thread toggle changes position while reading messages and unable to collapse thread → Thread toggle changes position while reading messages; then unable to collapse thread
Reporter | ||
Comment 3•23 years ago
|
||
Happened again today, all I did was view a message, post a response to the first
message in the thread, and when I returned, the toggle and been moved to the
wrong position.
Reporter | ||
Comment 4•23 years ago
|
||
I am set to View-->Messages-->Threads With Unread
The thread where it had happened in was one that had been auto-opened. Some NGs
show an auto-opened thread, other (well-behaved ones) leave them all closed.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•