[Users] [Bug 3951] New: First unread message selected surprisingly in some scenarios
noreply at thewildbeast.co.uk
noreply at thewildbeast.co.uk
Thu Jan 18 07:46:02 CET 2018
http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3951
Bug ID: 3951
Summary: First unread message selected surprisingly in some
scenarios
Classification: Unclassified
Product: Claws Mail
Version: 3.16.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: UI/Message List
Assignee: users at lists.claws-mail.org
Reporter: shai at platonix.com
I've seen three scenarios, which are really two, where the first unread message
in the folder is selected. In some of these scenarios it is annoying because it
moves the selection far from where it was (and where it was expected to be). In
all of them it is also annoying in combination with the "mark message as read:
when selected" setting, because if one is not careful, messages get marked as
read when the user wanted to keep them unread.
The first scenario is when the selected message becomes unavailable to display,
and not through an explicit delete or move operation. I've seen two cases of
this:
(1) When the selected message is moved by an action (e.g. marking as spam)
(2) When searching the folder, and the selected message does not match the
search criteria, but some other unread message does
The second scenario is the converse -- when you're in a folder, no message is
selected, but unread messages suddenly become available to display
(3) After searching a folder using criteria which match nothing, no message is
selected. Clearing the search criteria then selects the first unread message
Ideally, in case (1) above the behavior should be ruled by the next_on_delete
setting, and in cases (2) and (3) by the
default-selection-when-entering-a-folder setting. I'd also consider "no
selection" as reasonable behavior in all three cases, but this may just be my
bias (my default-selection-when-entering is set to "previously selected;
none").
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Users
mailing list