Files open in wrong window

[MetRonnie]

Using the File: Open command (Ctrl+O) to open a file from a restored (i.e. not maximized) window results in the file opening in another, pre-existing maximised window instead.

• VS Code Version: 1.61.2
• OS Version: Linux x64 3.10.0-1160.45.1.el7.x86_64

Commit: 6cba118ac49a1b88332f312a8f67186f7f3c1643
Date: 2021-10-19T14:58:13.605Z
Electron: 13.5.1
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0

Steps to Reproduce:

1. Open a VSCode window and maximise it
2. Open another VSCode window and make sure it is not maximised
3. In the unmaximized window, do Ctrl+O (or use the File: Open command from the command pallette) and open a file
4. The file will instead open in the maximised window

Using RHEL 7 (GNOME). I am unable to test this with the Inisders build as it's a work device. I cannot reproduce on Windows.

Does this issue occur when all extensions are disabled?: Yes

[sbatten]

@MetRonnie I don't have a great setup to test this at the moment, but can you confirm that this happens with any arbitrary file? Or more specifically, are the files you are opening part of the workspace of the maximized window?

[MetRonnie]

It happens for any file, even if doing Ctrl+O from the unmaximised window and choosing a file from that window's workspace, it will open in the maximised window instead

[vscode-triage-bot]

Hey @sbatten, this issue might need further attention.

@MetRonnie, you can help us out by closing this issue if the problem no longer exists, or adding more information.

[MetRonnie]

Still happening, I've updated the VSCode version and other details in the original post

[MetRonnie]

Something I have just noticed: if I have another maximised window of a different application in front of the maximised VSCode window, then (with the unmaximised VSCode window in the foreground) Ctrl+O from the unmaximised window does open the file in the correct (unmaximised) window

[vscode-triage-bot]

Hey @sbatten, this issue might need further attention.

@MetRonnie, you can help us out by closing this issue if the problem no longer exists, or adding more information.

[MetRonnie]

Still happening, Updated the version details in the original post

[vscode-triage-bot]

Hey @sbatten, this issue might need further attention.

@MetRonnie, you can help us out by closing this issue if the problem no longer exists, or adding more information.

[MetRonnie]

Still happening

[sbatten]

Thanks @MetRonnie, I tried to reproduce this again today and still am not having any luck. Can you reproduce this if you run with fresh user data and no extensions?

code --user-data-dir ~/fresh-data --extensions-dir ~/ext-dir