Bug 193076 - File manager does not keep previous position with dotted outline and pops to top
Summary: File manager does not keep previous position with dotted outline and pops to top
Status: RESOLVED DUPLICATE of bug 193549
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 4.2.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-18 05:28 UTC by gene smith
Modified: 2009-08-23 21:39 UTC (History)
1 user (show)

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 gene smith 2009-05-18 05:28:36 UTC
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

This is a bit hard to described but in my opinion it worked "correctly" in konqueror 3.5.x but is broken in 4.2.x. In "detailed" view in 3.5.x when you click on a folder icon to go into that folder, a dotted outline would appear around the icon before showing the files and directories in that folder. Then when you go "back" or "up" that same folder would maintain its outline and position on the screen. You could then go into other folders or files immediately above or below it.

In 4.2.x the outline on the folder icon appears before you go into to it. But when you come "back" or "up" the outline disappears and, the directory list moves back to the top (noticeable only if the directory list is long), causing you to loose your place as to where you previously were and requiring you to scroll back down to or near the folder you had just entered.

The only work around for this that I can find is to use the "lock to current location" view menu option. However, this causes a new window to appear when you click into the folder. This happen regardless of how the konqueror option "open folders in separate windows" is set.
Comment 1 gene smith 2009-05-27 06:41:54 UTC
This is the same problem described in bug 193549. I will add further comments to that bug.
Comment 2 FiNeX 2009-08-23 21:39:11 UTC

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