Bug 367851 - Folder View in Panel: deleting folders can break keyboard navigation
Summary: Folder View in Panel: deleting folders can break keyboard navigation
Status: RESOLVED DUPLICATE of bug 407889
Alias: None
Product: plasmashell
Classification: Plasma
Component: Folder (show other bugs)
Version: 5.7.2
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Eike Hein
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-26 11:57 UTC by stefanprobst
Modified: 2020-01-23 17:08 UTC (History)
5 users (show)

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 stefanprobst 2016-08-26 11:57:18 UTC
The FolderView panel-applet remembers the index of the selected file/folder in the previous subfolder, when using keyboard navigation. E.g. when navigating to the third subfolder in a directory and pressing left cursor to go back, (i) there is no visible selection, (ii) and pressing cursor down selects the forth item in the directory (if it exists, otherwise only cursor up is possible).

This is unexpected behavior, but can also totally break keyboard navigation in this scenario:


Reproducible: Always

Steps to Reproduce:
1. Create the following structure of empty directories:
~/foo/bar/dir1
~/foo/bar/dir2
~/foo/bar/dir3
2. Open the FolderView panel-applet for the Home Folder, and navigate to ~/foo/bar/ with the keyboard
3. Now select dir3, press Del to delete, select dir2, press Del
4. Press Left to go back to ~/foo

Actual Results:  
Cannot select anything by pressing Up or Down.

Expected Results:  
Be able to select something with keyboard.
Comment 1 Eike Hein 2016-09-14 12:30:27 UTC
*** Bug 368793 has been marked as a duplicate of this bug. ***
Comment 2 Alexander Mentyu 2017-12-13 12:35:10 UTC
sometimes bar folder isn't selecting with up or down arrow keys - even if not deleting dirs folders in step 3
Comment 3 Alex 2019-05-24 03:08:23 UTC
I can't reproduce this by following those steps, I tried a few times. But following the steps to reproduce bug 407889 I reliably get this issue.
Comment 4 Nate Graham 2020-01-23 17:08:48 UTC
Yep, looks like the same issue.

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