GNOME Bugzilla – Bug 262328
Selecting collapsed threads only selects the first message
Last modified: 2017-12-04 11:39:58 UTC
When selecting a collapsed thread, all messages of the thread should be selected (as with Ctrl-H), not the first one. I think it's more natural to do this way.
changing summary, it just took me too long to find this... :-)
*** Bug 306671 has been marked as a duplicate of this bug. ***
marking 227744 (GAL) as a dup of this one here: this bug here also refers to marking as read/unread and so on.
well...is this still gal's ETree?
*** Bug 227744 has been marked as a duplicate of this bug. ***
*** Bug 315611 has been marked as a duplicate of this bug. ***
3 duplicates, upping from enhancement to bug. Changing Component to Mailer. Removing keyword probabledup, adding usability instead. :)
I just tried dragging a collapsed thread from Inbox to a different folder. Only the first message in the thread moved. Is that a symptom of this bug, or should I raise a new bug report? Either way, dragging a collapsed thread from one mailbox to another should certainly move the whole thread, not just one message.
and the bug still exists in 2.30
also reported at: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/17752
*** Bug 790978 has been marked as a duplicate of this bug. ***
I made this work, but not for each action. It works for mark read/unread, delete, junk, archive messages and some other, but not for example for open selected messages or when saving selected messages as mbox. We can change the behaviour as needed. Created commit ad32bd159a in evo master (3.27.3+)
*** Bug 614896 has been marked as a duplicate of this bug. ***
*** Bug 777158 has been marked as a duplicate of this bug. ***
@Milan Thank you, so much! I'm experiencing the same problem as described by @Dooglus. > I just tried dragging a collapsed thread from Inbox to a different folder. > Only the first message in the thread moved. Has this been resolved too or should we open a separate issue?
(In reply to Michael Heyns from comment #15) > Has this been resolved too or should we open a separate issue? Drag&drop of a collapsed thread is covered in the above change, whole thread is used, instead of the top collapsed message only.