Change:
if (item.stale || !item.row.domNode.parentElement) { const referenceNode = this.items.at(index + 1)?.row?.domNode ?? null; <del> this.rowsContainer.insertBefore(item.row.domNode, referenceNode); </del> <ins> if (item.row.domNode.parentElement !== this.rowsContainer || item.row.domNode.nextElementSibling !== referenceNode) { this.rowsContainer.insertBefore(item.row.domNode, referenceNode); } </ins> item.stale = false; }

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.87.0 OS Version: Windows 10 Steps to Reproduce: vscode lose focus. on folders or files in File Explorer. If clicking on an already opened file in File Explorer, it opens normally without the need for a double-click.
It happens to me as well with the latest update Version: 1.87.0 (Universal) Commit: Date: 2024-02-27T23:42:56.944Z Electron: 27.3.2 ElectronBuildId: Chromium: 118.0.5993.159 18.17.1 V8: 11.8.172.18-electron.0 OS: Darwin arm64 23.3.0 maybe a dupe of , but this hadn't happened to me until the last couple of days.
Same problem here. I think that it appeared on latest update. Version: 1.87.0 Commit: Date: 2024-02-27T23:42:16.599Z Electron: 27.3.2 ElectronBuildId: Chromium: 118.0.5993.159 18.17.1 V8: 11.8.172.18-electron.0 OS: Linux x64 5.10.0-28-amd64
Same issue
Same for me, it didn't happen until a few weeks ago. It's very annoying since the hover state works as expected, but clicking the hovered file doesn't do anything (the first time).

I updated to 1.87.2 yesterday, I don't recall which version I was on prior to that, and I'm experiencing this behavior now too. It's really annoying because I keep thinking I selected a file only to realize it's not actually open and I have to click on it again. Version: 1.87.2 (user setup) Commit: Date: 2024-03-08T15:20:17.278Z Electron: 27.3.2 ElectronBuildId: Chromium: 118.0.5993.159 18.17.1 V8: 11.8.172.18-electron.0 OS: Windows_NT x64 10.0.
I'm still working on reproducing this on my Mac. Maybe I cannot due to lack of dual monitors on this screen. If anyone feels like doing some investigation you can bisect versions of VS Code to find when the regression occurred using
I have the same problem. Version: 1.87.2 (system setup) Commit: Date: 2024-03-08T15:20:17.278Z Electron: 27.3.2 ElectronBuildId: Chromium: 118.0.5993.159 18.17.1 V8: 11.8.172.18-electron.0 OS: Windows_NT x64 10.0.
I ran and that ended with the following: Commits I tried running but I keep running into issue after issue getting the code to build and finally just gave up. Hopefully that's enough information to point someone else in the right direction. There was one commit I tried where it seems like when the application first started I was able to click on a file and it took focus, but if I waited a little bit and then tried it had the behavior we're seeing now where it focused the tree view and then required a second click to focus the file. I'm not sure which one that was though. Based on my console history it might have been .
Thanks since were you able to repro would you be able to bisect this? I see one list commit in that range and that's the only possible culprit I see just by glancing at commit names
Thank you very much, but the issue hasn't been fixed.

I have submitted a demonstration
Confirms it is fixed here Just in case someone doesn't read the other thread