Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Bug: Arrow-key navigation in Details layout doesn't start at the top after opening a folder

Open Beginner friendly
#19,047 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
66/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
frontend

Research direction

Start by locating the Details layout’s arrow-key navigation and folder-opening behavior in the Files codebase; the issue does not name a file or test. Reproduce the steps with the listed folder structure, then check that the first Down press after opening folders b and c selects a. Confirm the fix by repeating both cases in Details layout.

Written by the indexing model from the issue text.

Description

area - accessibility
Description

In the Details layout, the first arrow-key press after opening a folder can select the wrong item. Instead of starting at the top of the new folder, the selection starts from the position of the item that was focused in the previous folder.

Steps To Reproduce
  1. Create this folder structure:
    a/
      b/
      c/
      d/
    b/
      a/
      b/
      c/
    c/
      a/
      b/
      c/
      d/
    
  2. Open the parent folder in Files using the Details layout.
  3. Use the arrow keys to select folder b (the 2nd item) and press Enter to open it.
  4. Press Down.
  5. Expected: the first item (a) is selected.
    Actual: c (the 3rd item) is selected.
  6. Go back, open folder c (the 3rd item) and press Down.
    Expected: the first item (a) is selected.
    Actual: d (the 4th item) is selected.
Files Version

4.3.0.0

Windows Version

10.0.26200.9457

User ID

No response

Log File

debug.log

Dominant language
C#
Stars
46.3k
Forks
3k
Avg merge
2d 6h
Merged PRs (30d)
23

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from files-community/Files

All issues in files-community/Files

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.