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
fix: maximized window bounds when toggle setResizable #40503
fix: maximized window bounds when toggle setResizable #40503
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested and verified to work as described - note though that the reported bounds don't change, it's a visual change that occurs when thickFrame is removed.
Release Notes Persisted
|
I have automatically backported this PR to "26-x-y", please check out #40580 |
I have automatically backported this PR to "27-x-y", please check out #40581 |
I have automatically backported this PR to "28-x-y", please check out #40582 |
Description of Change
Currently when we toggle setResizable function on maximized window then this window will change bounds and will not be equal to screen bounds.
This is happening because when we toggle setResizable then also HWNDMessageHandler::SizeConstraintsChanged() is called, where WS_THICKFRAME window style is removed.
Solution for this issue is to add WS_THICKFRAME for maximized window even if window is not resizable.
Checklist
npm test
passesRelease Notes
Notes: Fix problem with bounds of maximized window when toggle BrowserWindow.setResizable function.