311887 - Ignore Thread consequences

Status: RESOLVED WORKSFORME

(Thunderbird :: Mail Window Front End, defect)

Description

[Csaba Gabor]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051007 Firefox/1.6a1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051007 Firefox/1.6a1

Suppose you are reading a newsgroup where one of the threads has multiple
messages (suppose 3 or more), with View / Sort by preferences set as (Order
received; Descending; Threaded).

Do a Ctrl+a then K to ignore all messages.
Now click on a thread with at three or more messages.
Now press the right arrow to expand it.
Now press K twice.

Notice that you are still at that thread, and it is selected.  That's good.  The
thread is closed, however.

Now expand the thread again using the right arrow key and press the down arrow
key to go to the 2nd message in the thread.
Now press K twice.

The focus has disappeared!  That's not so good.  Thunderbird attempted to go to
the first next message (viewing the message list as circular) and didn't find it
so it placed the point just before the first message.
If you now press the down arrow key, you'll see that focus is on the first message.

Tested using Thunderbird version 1.5 Beta 2 (20051006)

Reproducible: Always

Steps to Reproduce:



Expected Results:  
I would like to recommend the following:

1.  Have a preferences setting that determines
    the message shown after a K is pressed:

A.  Next unread message:
        Next unread message (or first message),
        and collapse all threads just marked ignore
B.  Same message:
        The same one, and don't collapse anything
C.  First message in thread:
        The first message in the thread of the currently shown message,
        and collapse all threads just marked ignore

If A is used and there is no currently unread message, then the first message in
the first thread should be selected.

Csaba Gabor from Vienna

Comment 1

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Reporter, does the issue still occur in the latest supported 2.0.0.x / Shredder trunk nightlies?

(1.5.0.x is now end-of-life and the latest supported 2.0.0.x is 2.0.0.16)

Comment 2

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Reporter, does the issue still occur in the latest supported 2.0.0.x / Shredder trunk nightlies?

(1.5.0.x is now end-of-life and the latest supported 2.0.0.x is 2.0.0.16)

Comment 3

[René Falk]

I'm not the Reporter, but it seems that the issue don't occur in TB 2.0.0.16.

Comment 4

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Resolving WFM per comment #3.