Bug 306790

Summary: Dolphin - Expandable Folders: expansion status of nested folders is "forgotten" after an upper level folder is collapsed and then expanded again.
Product: [Applications] dolphin Reporter: mechaweb
Component: view-engine: details modeAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: 2.0   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description mechaweb 2012-09-14 13:48:31 UTC
Package: dolphin
Version: 4:4.8.4-1 

This issue is present when the "Details" view is used with the "Expandable Folders" feature of Dolphin.

If two or more levels of nested folders are "expanded" and afterwards the top-level folder is collapsed, the expansion status of those nested folders is forgotten and they all appear as collapsed. 

This issue was not present of prior versions of Dolphin.

Reproducible: Always

Steps to Reproduce:
( 1 ) Setup Dolphin to use the "Details" view and enable the "Expandable Folders" feature.

( 2 ) Select a folder tree with multiple nesting levels and expand at least two levels. Here is an example of what would it looks like:

- Folder1
    |_ + Folder1-1
    |_ - Folder1-2
        |_ - Folder1-2-1
            File1
            File2
            File3
    |_ + Folder1-3
+ Folder2
+ Folder3

( 3 ) Collapse the top-level folder (e.g. "Folder1"). As expected, it looks like the following:

+ Folder1
+ Fodler2
+ Folder3

( 4 ) Expand again the collapsed folder (e.g. "Folder1"). Instead of opening the branch structure as left in ( 1 ), lower-level branches will remain collapsed. It would look like this:

- Folder1
    |_ + Folder1-1
    |_ + Folder1-2
    |_ + Folder1-3
+ Folder2
+ Folder3



Expected Results:  
The expected result is that Dolphin recalls the expansion status of lower-level branches after the top-level branch is collapsed, as it previously worked.
Comment 1 Frank Reininghaus 2012-09-17 12:07:31 UTC
Thanks for the report! This issue has been reported already.

*** This bug has been marked as a duplicate of bug 304363 ***