Bug 251639 - Scroll position not remembered when going back in history in file open/save dialog
Summary: Scroll position not remembered when going back in history in file open/save d...
Status: CONFIRMED
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: Open/save dialogs (other bugs)
Version First Reported In: 5.45.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2010-09-18 09:44 UTC by Victor Yang
Modified: 2024-06-27 20:04 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Victor Yang 2010-09-18 09:44:57 UTC
Version:           unspecified (using KDE 4.4.2) 
OS:                Linux

In the open file dialog (I think it's the KFileDialog class), your scroll position among the list of files and directories is not remembered when going back in the browsing history -- the list always returns to the top.  This limits the functionality of the dialog for users who prefer using the keyboard to navigate instead of the mouse.

konqueror had a similar feature added/fixed:
https://bugs.kde.org/show_bug.cgi?id=193549

Reproducible: Always

Steps to Reproduce:
1. open any kde application from which to open a file
2. choose "open" from the "file" menu
3. use the cursor keys to select a sub-folder that is not listed first
4. press alt-back -- or whatever your global short-cut is for "back"

Actual Results:  
The folder selected in step 3 is not highlighted or otherwise marked. Pressing any cursor key will immediately highlight the first directory.

Expected Results:  
The directory selected in step 3 is marked or highlighted so that pressing the cursor keys will resume navigation from where the user left off; similar to the behavior implemented for the following bug:
https://bugs.kde.org/show_bug.cgi?id=193549
Comment 1 Frank Reininghaus 2010-09-18 11:46:29 UTC
Thanks for the bug report! I can reproduce the issue in trunk.
Comment 2 Nate Graham 2018-04-13 15:30:54 UTC
Still an issue in KDE Frameworks 5.45.