Bug 276000 - section remains even after the last threaded message is moved out of it
Summary: section remains even after the last threaded message is moved out of it
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: 2.1.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-18 20:58 UTC by Ivan D Vasin
Modified: 2017-01-07 21:54 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan D Vasin 2011-06-18 20:58:13 UTC 
Version:           2.1.0 (using KDE 4.6.4) 
OS:                Linux



Reproducible: Didn't try




OS: Linux (x86_64) release 2.6.38-10-generic
Compiler: cc
Comment 1 Ivan D Vasin 2011-06-18 21:07:28 UTC 
oops, i hit Enter on accident.


by "section" i mean one of the sections in the message list that group messages so that they have headings (typically by date) that can be clicked to expand or collapse the view of the group.

steps to reproduce:
1. set the message list to be threaded.
2. apply a filter that narrows down one of the past sections to one message.
3. send a reply to the message.

actual results:
1. after being sent, the message appears in today's section in the message list.
2. the header for its previous section, which is now empty, remains in the message list.

expected results:
1. as above
2. the header for its previous section is removed unless another message was added to it prior to the reply bumping the thread up to today.
Comment 2 Denis Kurz 2016-09-24 18:23:33 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 3 Denis Kurz 2017-01-07 21:54:51 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.