[Bug 279555] New: Place in list lost when messages are refreshed

[Jonathan M Davis]

https://bugs.kde.org/show_bug.cgi?id=279555

           Summary: Place in list lost when messages are refreshed
           Product: kmail2
           Version: unspecified
          Platform: Archlinux Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: message list
        AssignedTo: kdepim-bugs at kde.org
        ReportedBy: jmdavisProg at gmx.com


Version:           unspecified (using KDE 4.7.0) 
OS:                Linux

Kmail lists itself as 4.7.0 just like KDE, so I don't know what application
version number (2.x) it is, hence why I left it as unspecified.

If you have a message selected in the message list and the message list
refreshes (e.g. when the account in synced with the server), the list goes away
briefly and then comes back, and when it does, you often lose your place in the
list. It does _not_ go back to the message that you had selected previously. I
believe that it usually goes to the first message in the thread and collapses
the thread (probably because the thread has no unread messages in it and the
standard mailing list has those threads collapsed when you first go to a folder
with a mailing list in it).

The state of the message list should _not_ change when the messages are
refreshed beyond what the current viewing mode does for new messages. That is,
if a thread is expanded, it should stay expanded. If a message is selected, it
should stay selected. But it does make sense for a thread to be newly expanded
if it was collapsed before and a new message appeared in it. IIRC, kmail 1 left
such threads collapsed though, and you had to select another folder and then
reselect the first for those threads to be expanded. However, that behavior is
far superior to kmail 2's behavior, so if it's a choice between leaving the
threads alone completely on a refresh and rearranging it all as if you had just
selected that folder, I'd go with leaving everything alone.

You should _not_ lose your place in the message list simply because the message
list was refreshed. This is a major regression from kmail 1. So, at minimum,
kmail 2 needs to remember your place on a refresh and restore it. However,
ideally, it wouldn't collapse any threads which were expanded either.

Reproducible: Always

Steps to Reproduce:
1. Select a folder with a standard mailing list in it.
2. Select a message which is no the parent message in a thread and which is in
a thread with no unread messages in it.
3. Sync the messages in that account when a new message is going to be put into
the folder that you've currently selected a message in.

Actual Results:  
The whole message list refreshes as if you'd newly selected the folder and the
message which is then selected is _not _the message that you had selected
before.

Expected Results:  
The message that you had selected before _stays_ selected, and threads which
were expanded before _stay_ expanded.

If it matters, I'm using accounts with disconnected IMAP.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.