Version: (using KDE 4.2.0) OS: Linux Installed from: Mandriva RPMs I have expanded thread which is collapsed (e.g. using keyboard ','). What happens now depends on which exactly message was selected at the point of collapsing. If currently selected message is the first in thread, thread becomes selected If currently selected message is not the first one, *nothing* gets selected at all. This makes working with threads more awkward than it could be because to do anything with whole thread requires extra mouse movement to select it.
What I see doing what you describes in kmail 1.11.90 (kde 4.2.62) is: I expand a thread with lots of levels, select one of the inner mails. Press , to collapse the thread, and the previous selected mail is still selected. When I press ->, it expands again the thread and selects the next mail in the thread. Should it select the next thread when pressing -> ? This is what happens when the thread is collapsed. I let the developers decide what is the desired behavior.
*** Bug 187433 has been marked as a duplicate of this bug. ***
as described in my dupe report, i think the old behavior (pre kde-4.2) is the correct behavior. it's more intuitive and allows for faster (proper?) keyboard navigation. current behavior makes the keyboard thread collapse kind of useless as you still need the mouse, and with the collapse keys on the right side of the keyboard (and right handed people being the majority) ...
(In reply to comment #3) Thank you for excellent explanation which is much better than mine. I fully agree with you; and actually this makes the case not a simple bug but regresion.
Still same behavior in Kmail 1.12.1 (KDE 4.3.1 - Kubuntu 9.04). Example: Expanded view with message selected: -Thread 1 Re: Thread 1 -SELECTED- Re: Thread 1 +Thread 2 After collapsing (nothing apparently selected): +Thread 1 +Thread 2 The first thread message should get selected after collapsing: +Thread 1 -SELECTED- +Thread 2 This way you can move up and down the list, delete the whole thread with one key (as Kmail with KDE 3.5), otherwise a mouse click is needed. Hope it gets fixed soon.
Thank you for taking the time to file a bug report. KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2. We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.