Bug 354515 - folder list does not remember folded states after quick search
Summary: folder list does not remember folded states after quick search
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: folders (show other bugs)
Version: 4.14.1
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-28 17:19 UTC by Manny
Modified: 2018-01-31 16:52 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Manny 2015-10-28 17:19:00 UTC
The folder list expands fully on quick search and does not remember folded
states. The consequence is that I end up with an unmanageable list
of foldes in the folder list. The 'old' kmail behaved much better,
remembering folded states and not automatically unfolding to the searched
for place and below. Given the number of matches I have, pretty much
everything shows after most searches. Try entering 'e...', the e is rather common...

Reproducible: Always

Steps to Reproduce:
1. Have a large folder hierarchy list, fold it so only the top level shows.
2. Do a quick search to select a folder lower down (enter a few characters, start
    with a common one!)
3. Delete the characters, check folder list. It stays expanded, at least one
   level below the search.


Expected Results:  
I liked the kmail1 behavior. At least, it should revert to the pre-search
folded state!
Comment 1 Denis Kurz 2017-06-23 20:17:47 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-01-31 16:52:52 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.