files-community / files-community/Files
Bug: Double clicking file in parent column causes file area to scroll (Columns View)
- Dominant language
- C#
- Stars
- 45.4k
- Forks
- 2.9k
- PR merge metrics
- PR metrics pending
Description
### Description
Double‑click behavior inconsistency in Columns view
**Folder structure:**
Desktop
└─ Test_A
├─ Layer_1
│ ├─ 2D
│ ├─ 3D
│ ├─ Comp
│ │ ├─ (Footage)
│ │ └─ Word_A.txt
│ └─ Refs
└─ Word_B.txt
**Observation (Columns view enabled):**
https://github.com/user-attachments/assets/f3926f05-06ee-4ff5-a0f8-5262ccd4d424
-------- macOS --------
https://github.com/user-attachments/assets/4640994a-520b-4647-bbbb-28afb9e28b08
-------- Files --------
- In **macOS Finder**, as shown in the attached video, after double‑clicking `Word_A.txt` to open it, I can immediately double‑click `Word_B.txt` without any unexpected window jumps. The navigation remains smooth and predictable.
- In **Files**, however, due to the current window‑handling logic, double‑clicking `Word_B.txt` results in the following misbehavior:
1. The first click of the double‑click selects `Word_B.txt`, which triggers a window navigation (folder content jumps).
2. Because the window jumps during that first click, the second click of the double‑click is no longer registered on `Word_B.txt` – instead, it lands on the empty background area of the desktop (or an unintended region).
**Impact:**
This breaks the intuitive double‑click workflow, especially when users need to quickly open multiple files in succession. The erratic navigation forces users to re‑acquire the target file, reducing efficiency and causing confusion.
**Suggested alignment:**
Adopt the robust focus and navigation behavior seen in macOS Finder, where double‑click actions are reliably processed without intermediate window jumps, ensuring that both clicks of the double‑click are consistently applied to the intended file.
### Steps To Reproduce
As mentioned above.
### Files Version
4.2.0.0
### Windows Version
10.0.26200.8737
### User ID
5be1ab97-a6f8-4ceb-8e51-64d2d86df27a
### Log File
[debug.log](https://github.com/user-attachments/files/29999440/debug.log)
Contributor guide
Assessment
This issue has not been assessed yet.