Bug 319499 - On every refresh of mailbox from server, Kmail jumps to next message in message list automatically.
Summary: On every refresh of mailbox from server, Kmail jumps to next message in messa...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: 4.10.3
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-08 02:15 UTC by Kanwar Plaha
Modified: 2017-01-07 21:36 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 Kanwar Plaha 2013-05-08 02:15:03 UTC
When viewing a message, if a refresh of the mailbox is done from the server, the focus jumps to the next message automatically -- either in the current thread (if a reply exists) or the previous thread.
If left on its own, the focus in message list keeps shifting down on each refresh.

Reproducible: Always

Steps to Reproduce:
1. Start Kmail
2. Configure a mail account to receive mail from
3. Wait for each refresh to see focus in message list jump to next message automatically
Actual Results:  
Focus was lost from the message I was reading.

Expected Results:  
Focus should not shift from one message to another automatically in the message list. 

A refresh of messages from the mail server should not affect my reading of any message and the focus in message list must remain on the message being read at that time.
Comment 1 Denis Kurz 2016-09-24 18:13:08 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:36:47 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.