Bug 369724 - "Next unread message" after "Delete" leaves two messages selected
Summary: "Next unread message" after "Delete" leaves two messages selected
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: 5.3.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-03 16:58 UTC by Tristan Miller
Modified: 2022-11-25 05:22 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 Tristan Miller 2016-10-03 16:58:57 UTC
Say I have a folder with three consecutive, unread messages, which I will call A, B, and C.  If I select A, then delete it by pressing the Delete key, then KMail deletes A and automatically selects and displays the next message in the list, B.  If I then type +, the keyboard shortcut to move to the next unread message, then KMail selects and displays C, but leaves B selected too.

I think this behaviour is wrong.  As soon as I advance to the next message with +, the previously selected message should be unselected.

This problem is consistently reproducible, but only when using the keyboard shortcuts.  If I use the "Move to Trash" command from the Edit menu, and the "Next Unread Message" command from the Go menu, then the problem does not occur.

Reproducible: Always
Comment 1 Justin Zobel 2022-10-26 03:07:05 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-11-10 05:12:15 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2022-11-25 05:22:31 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!