19618 - ThreadedView: unread msgs buried in already-read msgs

Status: VERIFIED FIXED

(SeaMonkey :: MailNews: Message Display, defect, P3)

Description

[Chris McAfee]

Thread View, R=read, U=unread

 > R msg #1
    U msg #2

In this example, if I collapse the thread (click on triangle
next to msg #1), I can't find or detect that msg #2 is unread!
This is kinda bad, I'm missing some new mail occasionally.

Comment 1

[Chris McAfee]

4.x had the green spool icon, we don't have that icon here,
how do we show this?  Adding german.

Comment 2

[scottputterman]

I haven't implemented this yet so even if there is an icon, it wouldn't do any
good :-)

Comment 3

[Richard Zach]

Don't need an icon, just display the first msg in thread bold (like unread
msgs).

Comment 4

[scottputterman]

I think there are some usability issues with doing that.  Currently bold means
that that message is unread.  I think that if someone clicked on the green
diamond they would expect it to bold/unbold regardless of the children's read
state.  I would at least.  Of course we could do something besides bold which
would make these two states not conflict.

Currently we are proposing expanding threads when you open them.  In which case
the unread message count on the top level thread already serves as an indicator.
However, I think the icon just gives added feedback.

Comment 5

[Phil Peterson]

Maybe I'm biased, but I think we should continue to do what 4.x does: there's a
green arrow on the thread icon when the thread has unread children. Bold is for
the message, not for the thread. Newness is indicated separately with a green
arrow on the message icon rather than the thread icon.

Scott, do you think this is a beta stopper?

Comment 6

[scottputterman]

probably not.

Comment 7

[Chris McAfee]

If we don't implement something here, I'm going to
accidentally not-read some of my inbox; how can you
find the unread mail?  If spacebar-go-to-next-unread
is working I might be convinced that this could be
moved to post-beta status.

Comment 8

[scottputterman]

2 ways that I can think of. First, the unread message column count tells you if
a threads has messages (I recognize that this number isn't always accurate but I
think there's a bug on it).

The second is code that I hope to check in this week which is that I now open up
the entire thread when you click on a twisty (you will have the ability to close
parts of the thread once they are open assuming I'm not asked to take that out)
and the Next Message button will find unread messages and open threads to take
you there.

I guess it depends on what this bug means.  From your original comment, I think
the Next Message button will probably solve the problem.  But this bug quickly
turned into the green spool bug and that is the part that I don't think needs to
be fixed by beta (I'm not saying it won't, but I was asked if I thought it was a
beta stopper which I don't think it is).

Comment 9

[Phil Peterson]

Since we currently expand the whole thread, as putterman described on 12/21, I
don't think this is a beta stopper.

Comment 10

[laurel]

To confirm re-test for b1 bug triage:
1.  Yes, Next Unread will open the entire thread and land on unread message,
even a few levels down in most cases (entire thread is expanded).
2.  No, Next Unread will not find and land an unread message if the unread item
is in a collapsed sublevel of an otherwise expanded thread.
2.  Yes, when expanding via twistie the entire thread is displayed.

Comment 11

[selmer (gone)]

Mass moving to M16 to get these off the M15 radar.  Please let me know if this
is really an M15 stopper.

Comment 12

[scottputterman]

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

Comment 13

[scottputterman]

moving to M18 and nominating for beta3.

Comment 14

[lchiang]

+ per mail triage

Comment 15

[selmer (gone)]

Elevating priority since we couldn't convince ourselves to cut this today.

Comment 16

[lchiang]

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

Comment 17

[scottputterman]

I have a fix for this but I don't have any icons for the classic skin.  This 
seems to have the side effect of making the thread column non existent. So I 
might just check in the modern images into the classic skin to make this work 
until someone replaces them.

Comment 18

[David :Bienvenu]

adding self to cc list.

Comment 19

[jglick]

Putterman, what classic images do you need?  See attachment to follow.

Comment 20

[jglick]

Attachment: Thread New Classic

Comment 21

[jglick]

Attachment: Thread New Expanded Classic

Comment 22

[jglick]

Attachment: Thread Classic

Comment 23

[jglick]

Attachment: Thread Expanded Classic

Comment 24

[Phil Peterson]

PDT thinks this is a P3. 

Comment 25

[scottputterman]

fix checked in.

Comment 26

[fenella]

Linux (2000-09-11-08 M18)
Win32 (2000-09-11-08 M18)
Mac (2000-09-08-20 M18)
This problem has been fixed.