Navigation through mails should be possible using the arrow keys, (even if the focus is on the mail preview window) - like in Thunderbird ("up" for the previous message and "down" for the next message). Reproducible: Always Steps to Reproduce: 1. Focus a mail from the list 2. Hit up and down key Actual Results: Nothing happens Expected Results: The next or previous mail should be displayed in the preview window.
This is actually a regression from earlier KMail versions (pressing left/right changed the messages, pressing up/down scrolled in the message view). Can you change the priority from "wishlist" to actual "bug"? When pressing SHIFT when "navigating" with the arrow keys, it's even a combination of the old and the new behaviour ;-)
Version ? it's fixed in 5.0.2 or 5.0.3
In my case: The Archlinux package version is 15.08.3-2 (amd64). The About dialog says 5.0.3, using frameworks 5.17.0 and Qt 5.5.1.
I realized that I only tried up and down keys and not left and right... So in version 4.14.10 left and right is for navigating to the next or previous message and up and down is for scrolling inside the message. Shift + left and right is for selecting mails from the current mail n times up / down when you hit left / right n times and Shift + up / down is for extending the selected mails range up and down. I really like the way it is, so this issue can be closed... The problem was that I wasn't firm with this features...
@Sebastian So for you left/right works? I am using the aforementioned versions and left/right are _not_ working for me. It only opens/closes message trees of grouped threads but is not switching between messages.
Oh, yes left and right navigates to the previous / next message... But I did not find a way to open the message tree... If it doesn't work, you can reopen this...
I just rechecked - this bug is still valid for a "pure" KF5 installation as well as one on a computer just recently updated from KDE4. The shortcuts in the menu for Next and Previous message are set to "none". So I am a little bit confused why it works on your setups but not mine. @Laurent: Shall I open another report or can you change the status here?