Bug 322455 - status filter "unread" unusable
Summary: status filter "unread" unusable
Status: RESOLVED DUPLICATE of bug 259813
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: 4.10.5
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-16 21:27 UTC by Shai
Modified: 2013-07-17 17:25 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Shai 2013-07-16 21:27:33 UTC
When the status filter on the message list is set to "Unread", every message whose status changes to "read" is immediately removed from the list (except when messages are threaded and the message has an unread child). This may seem to make sense, but is in fact surprising and unwelcome; the fact that a message I am looking at is already gone from the list, and if I press right-arrow (next message) then left arrow (prev message) I won't get back to it, is a real hindrance.

Reproducible: Always

Steps to Reproduce:
0. In the settings->Configure Kmail->Misc->Folders check "mark selected message as read after" and set a small number of seconds (I use 2).
1. Choose a mail folder with unread messages.
2. Change filter status to "Unread"
3. Navigate the message list, preferably using the right-left arrows, to read the messages in the preview pane
Actual Results:  
Every thread you go through is removed from the list, and then you can't go back to it.

Expected Results:  
Filtering should be applied when the filter is set, but messages should not be removed automatically after that (except when deleted or moved, of course, but that isn't really "automatically").

This is a regression from KMail1, which had the correct behavior.
Comment 1 Laurent Montel 2013-07-17 17:24:30 UTC
Still duplicate
Comment 2 Laurent Montel 2013-07-17 17:25:19 UTC

*** This bug has been marked as a duplicate of bug 259813 ***