158217 - New single/topic msgs show with collapsed twisty in Threads with Unread

Status: VERIFIED FIXED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[laurel]

Not a new bug -- I thought I'd seen this reported before, couldn't immediately
locate existing bug... maybe it was just a mention in some other bug report. 
Anyway, getting it in for the record.

When you get new messages in a folder or newsgroup set to View|Messages|Threads
with Unread, any new message which is a single/topic message will show in the
thread pane as if it's collapsed; as if it had child messages/replies even
though it doesn't.

Steps:
1.  Open a mail Inbox or newsgroup, set to View|Messages|Threads with Unread.
2.  Send a new message, get the message.

Result:  Threads with Unread view shows the new/topic message with a twisty
indicating a collapsed thread, even though it's a single message having no
replies/children.

Expected:  The view should show no expand/collapse twisty next to the
single/topic message.

Comment 1

[Mikhail Sogrine]

Confirm for 1.1b Win2K

Comment 2

[Jason M. Abels]

Confirm on WinXP, moz build 2002072304

Comment 3

[Jason M. Abels]

Correction to above comments. Bug is reproducable in 1.1b on WinXP, but does not
appear on 2002072304 Build.

Comment 4

[Jason M. Abels]

Build: 2002072408 (I believe this has been the behaviour in all 1.1b builds)


This bug only appears on the first view of the folder after new messages have
arrived. If you select another folder, and then go back, the folder is displayed
properly without a widget on messages with no threads underneath.

So, this appears to happen when the messages are retrieved from the server, but
when returning to view the folder again, it does not appear. Could it be a bug
in retrieval?

Comment 5

[laurel]

nominating for next release

Comment 6

[Thomas F. O'Connell]

FWIW, i'm seeing this in 1.1 (Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US;
rv:1.1) Gecko/20020826) on Jaguar.

Comment 7

[laurel]

*** Bug 145099 has been marked as a duplicate of this bug. ***

Comment 8

[David Tenser [:djst]]

How can bug 145099 be a duplicate of this one, when this one was reported two
months later? The only valid reason for that would be if this bug had a patch
waiting for review, which it hasn't. 

The only explanation I can find is that the bug reporter of this bug wants this
to be "his" bug! And the cc list for that bug was not honored either... Manually
adding myself to cc!!

Comment 9

[laurel]

I think you're taking it all too seriously... this one was already/also
collecting information and is nominated.  As I mentioned when reporting this, I
knew I'd seen it before, but when querying I didn't find yours because I didn't
query for "alone message", etc.-- I used different lingo.

We don't really tally who finds what first, you know. Lighten up.

Comment 10

[David Tenser [:djst]]

I'm not really upset, sorry if I made it sound like that. Bug 145099 wasn't even
reported by me... :) I was just surprised so see how a duplicate could get
priority over the original bug when no patch was created. I did not see it was
nominated.

Anyway, this is the first time I've seen that the cc list was not transfered to
the new bug. The reporter of the original bug has even voted for that bug.

Adding him to cc. Can't transfer his vote though.

Comment 11

[David Tenser [:djst]]

<ot>
The vote was not from the reporter, it was from someone else. I also realize
that the reporter was already added to this cc when I did it. I will shut up now! :)
</ot>

Comment 12

[David :Bienvenu]

taking; fix upcoming

Comment 13

[David :Bienvenu]

Attachment: proposed fix

check how many messages are in the new thread before setting the has children
and collapsed bits.

Comment 14

[David :Bienvenu]

Cavin, can I get a review? thx.

Comment 15

[Cavin Song]

Comment on attachment 104215 [details] [diff] [review]
proposed fix

r=cavin.

Comment 16

[(not reading, please use [e-mail] instead)]

Comment on attachment 104215 [details] [diff] [review]
proposed fix

sr=sspitzer

Comment 17

[David :Bienvenu]

fixed on trunk.

Comment 18

[laurel]

OK using nov19 commercial trunk: win98, linux rh8.0, mac OS 10.2