Closed
Bug 188774
Opened 22 years ago
Closed 17 years ago
expanding and collapsing specific threads only makes messages appear several times
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: uri, Unassigned)
Details
Attachments
(1 file)
95.74 KB,
image/jpeg
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126 I've been viewing some threads on comp.os.ms-windows.programmer.win32, and I can't sem to collapse their view. when I try to expand and then collapse, I only get to see the same messages several times. for example, a thread started by "lz" on 1/9/2003 10:14 PM titled "FreeLibrary" - news://news.bezeqint.net:119/3E1DEE0B.F89E16F8@cs.cmu.edu, and a thread started by "Adam M. Fass" on 1/9/2003 11:47 PM titled "Turning off the monitor" - news://news.bezeqint.net:119/3E1DEE0B.F89E16F8@cs.cmu.edu. Reproducible: Always Steps to Reproduce: 1. view the above threads 2. expand the thread 3. collapse the thread Actual Results: the 1st message appears with several (copies of) messages from the thread. each time I expand and collapse, more copies of the same messages appear in the treeview. note: the "FreeLibrary" thread only seems to have one message in it Expected Results: show only the 1st message in each thread
just in case me description wasn't understood... see the "FreeLibrary" thread
Comment 2•22 years ago
|
||
please try a newer build - you may also need to remove the .msf file for this newsgroup for this problem to go away with a newer build. I believe this is a dup of an already fixed bug.
Status: UNCONFIRMED → NEW
Ever confirmed: true
thanks, bienvenu. I'm not accustomed to using non-released builds - should I expect to see this fixed in 1.3 Beta?
same bug still happens with 1.4b toda it happened with this thread: news://news.netvision.net.il:119/OEssd4qCDHA.1552@TK2MSFTNGP12.phx.gbl BTW, what and where is the mentioned .msf file ?
Comment 5•21 years ago
|
||
the .msf file is in your user profile directory, in the news server subdirectory - just do a search for a file with the same name as the newsgroup and a .msf extension. Since I don't have access to that news server, I don't know what thread it's happening on. Is it a public newsgroup?
my apologies - the group is microsoft.public.dotnet.framework.clr, as public as can be. I found the .msf file, but I doubt deleting it will help me - I only subscribed to this newgroup today, using 1.4b, so I don't have a build newer than this. I think this also proves this bug isn't fixed in 1.4b, right?
Comment 7•21 years ago
|
||
Is it this message? C# questions from C++ developer by "Alexander Galkin"? I did not see this problem expanding/collapsing this thread. Are you in the "unread only" view, or viewing all headers?
yep, that's the thread. I was viewing all headers. of that I'm certain. funny - now it doesn't reproduce. this bug is strange, but I'm sure I'll see it again.
Comment 9•21 years ago
|
||
Uri, the problem you saw might be just a temporary problem when headers arrive into an open newsgroup out of thread order - the already fixed bug I referred to earlier was a permanent problem (hence the need to delete the .msf file). However, I don't know of a reproducible case for a problem like this. Did you get new messages while you were reading the group? Or did you just open it and see the problem right away when expanding the thread?
Reporter | ||
Comment 10•21 years ago
|
||
to the best of my memory, I first subscribed, then "got new messages" (which only brings headers, right?), and only when that was done I started reading the messages in the group. does that answer your question?
Reporter | ||
Comment 11•21 years ago
|
||
I got the same problem today (this time moz 1.4) on another newgroup. whassup with this?
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•19 years ago
|
Assignee: sspitzer → mail
Comment 12•17 years ago
|
||
WFM version 2.0.0.6 (20070728) and trunk
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•