Bug 319128 - Can't use arrow keys to move between messages
Summary: Can't use arrow keys to move between messages
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: 4.10.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-30 17:56 UTC by Vincent Petry
Modified: 2017-01-07 22:14 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent Petry 2013-04-30 17:56:52 UTC
The arrow keys can't be used to switch between messages when the focus in on the message list.
This is a usability issue.

Reproducible: Always

Steps to Reproduce:
1) Make sure to have more than one message in the message list
2) Click on one message in the message list
3) Use the Up and Down arrow keys to move between messages
Actual Results:  
Cursor doesn't move on the message list, but the message preview scrolls up/down instead.

Expected Results:  
Cursor moves up and down

If I use the arrow keys with the Shift key pressed, it will successfully select the messages, so it seems that the focus is set properly on the message list, but for some reason the key event seems to go to the message preview.

Page up and page down also seem to affect the message preview instead of the message list.
Comment 1 Denis Kurz 2016-09-24 17:59:30 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:14:12 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.