-
Notifications
You must be signed in to change notification settings - Fork 30.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keep window maximized when screen resolution changes #90412
Comments
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
This sounds like the OS should take care of it. I doubt VSCode should do something specifically. |
@bpasero VS Code manages it's own window state. There is a setting to always start maximized for example, if the window was maximized last time VS Code was closed. A probably related issue is, if you use win+shift+left or win+shift+right to switch between displays it also doesn't maintain the maximized state. |
@johnendev would you mind filing an issue against Electron itself if you can e.g. reproduce with their app: https://www.electronjs.org/fiddle |
@bpasero I've tested Electron Fiddle and results are as follows Electron v6.1.6 (currently used by VS Code) Electron v6.1.7 Electron 7.0.0 Guess that means just wait for VS Code to upgrade to a newer version of Electron. I see it's in progress already: (#90371) |
@johnendev interesting, our insider builds already run with Electron 7. |
@bpasero ok, tested it on the insiders build and the maximized state is preserved correctly. |
Yes. |
Issue Type: Bug
When ever the screen resolution changes, the VS Code window becomes un-maximized.
The window should stay maximized.
This has been an issue for as long as I can remember using VS Code.
VS Code version: Code 1.42.0 (ae08d54, 2020-02-06T10:51:34.058Z)
OS version: Windows_NT x64 10.0.18363
The text was updated successfully, but these errors were encountered: