The scroll position resets to the top of the file list after viewing a file in an embedded viewer. Reproducible: Always Steps to Reproduce: Preconditions: 1. A directory containing more files than will fit on the screen, e.g.: $ cd /tmp $ mkdir repro-bug $ cd repro-bug/ for i in `seq 1 100`; do touch ${i}.txt; done; 2. Embedded viewer enabled (I have experienced this with both text files and PDF files): a. Settings -> Configure Konqueror... b. File Management -> File Associations c. Choose text group. Choose Show file in embedded viewer. (Or for PDF files, choose application group, then choose pdf; in Embedding tab, choose Show file in embedded viewer.) Steps to reproduce: 1. Navigate to directory containing more files than will fit in the window. 2. Scroll to the bottom of the list. 3. Click (or double-click) to open a file. The file will display in the embedded viewer. 4. Click the Back button. Actual Results: The scroll position is at the beginning of the directory. Expected Results: The scroll position is at the same place as before I opened the file. Note that the scroll position is correctly saved when viewing web sites. E.g. 1. Search Google for "konqueror bugs". 2. Scroll down to the bottom of the 10 results. Click one of the results. 3. Click the Back button. The Google search results page is redisplayed at the same scroll position as before. This makes it very inconvenient to open each file in a directory in sequence, e.g. when I'm looking at PDFs of my pay statements, I want to look at the 2014-01-03 pay statement, then the 2014-01-17, then 2014-01-31, etc., without having to scroll down from my first pay statement every time. I believe this worked correctly in Debian squeeze. I thought maybe wheezy got a bad release of konqueror, but now I've switched to jessie and the issue is still there.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!