GNOME Bugzilla – Bug 227744
Mark as read on a collapsed thread doesn't work properly
Last modified: 2005-07-15 15:53:05 UTC
Choosing "mark as read" on a collapsed thread only affects the first message in that thread. Steps to reproduce the problem: 1. Collapse a thread of unread messages. 2. Select the thread and chose "mark as read" Actual Results: Only the top message in the thread is marked as read. Expected Results: All messages in the thread should be marked as read. How often does this happen? Every time
well, this is the way I would personally expect it to work
I always thought selecting a collapsed thread would select every message in the thread. I usually select a number of threads that I don't find interesting and mark as read. I found it odd that the messages were still unread after doing that. Actually, when just selecting a single collapsed thread, I can see your point (just a matter of what you expect I guess), but when selecting a number of threads and messages (with shift), usually every thing every thing gets selected and this would include all messages in the thread as well or?
When I think about it, you're probably right. When selecting a single collapsed thread it should probably behave as it's doing right now. I still think it's not working right when shift-selecting a number of threads though.
moving this to gal, as etable is responsible for all selection handling. perhaps shift-click could select the whole tree, even if hidden. or perhaps nothing should change.
product design team needs to make the choice here before anyone can implement anything... not that this is high on any todo list since no one is maintaining gal, but ah well.
I have the same bug here on version 2.2.1.1 but I don't have to collapse the thread. I select the first message of a thread. It becomes read. I type Ctrl+h to select the whole thread, then Ctrl+k to mark as read. Nothing changes, and only the first message is marked as read. If I type Ctrl+Shift+k to mark the whole thread as unread, and then Ctrl+k to mark as read, all the messages in the thread are correctly marked as read.
nicolas, comment #6: cannot reproduce that. this is a duplicate of bug 262328. *** This bug has been marked as a duplicate of 262328 ***