Closed
Bug 136825
Opened 22 years ago
Closed 22 years ago
displayed news entries get duplicated when (+) then first entry in thread are selected
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 123858
People
(Reporter: philbrunner, Assigned: sspitzer)
References
()
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9+) Gecko/20020409 BuildID: 20020409 Viewing news as threads. Click the + button to expand; then click the first entry in the thread. Immediately after message is displayed, the - button changes to a + button. If you now click the erroneous + putton, the remaining entries in the thread are duplicated. Reproducible: Sometimes Steps to Reproduce: 1.Select threads in news display. 2.Click + button to expand the thread; + changes to - 3.Select the head message in the thread. Actual Results: The "-" (collapse) button turns to a "+" (expand) button immediately after the selected head message is displayed. If you now click the erroneous "+", expansion takes place; the non-head entries in the thread are all duplicated in the display. Expected Results: The "-" button should remain a "-" after the head entry is selected and displayed. Sometimes, this works o.k.; but usually you get the behavior noted. If at first you don't succeed, keep trying; eventually, the behavior will start and will continue. You can avoid this duplicate entries display if you select the head message before expsnding the thread. Everything will work as expected. Once you realize what is happening you can just ignore the behavior; you are able to display all messages and the duplicate display disappears the next time you open the news.
Reporter | ||
Comment 1•22 years ago
|
||
The behavior noted only occurs when the entire thread is unread.
Comment 2•22 years ago
|
||
Is this bug 123858?
Reporter | ||
Comment 3•22 years ago
|
||
Thanks! Yes, this is a duplicate of bug 123858, especially comment #9 with two comments: On occasion, I'm sure I've had the bug go away. Probably after a clean install, but it always seems to come back. And I'm a little amazed at how people's perceptions vary. I was hesitant to submit the bug since it appears to be non-harmful, just a minor annoyance to me. Others see it as a major problem! Guess I'm easily pleased. :) *** This bug has been marked as a duplicate of 123858 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 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
•