Bug 279555 - Place in list lost when messages are refreshed
Summary: Place in list lost when messages are refreshed
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: 4.7
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-06 20:45 UTC by Jonathan M Davis
Modified: 2017-01-07 21:49 UTC (History)
0 users

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 Jonathan M Davis 2011-08-06 20:45:05 UTC
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.
Comment 1 Denis Kurz 2016-09-24 18:18:39 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 21:49:44 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.