-
Notifications
You must be signed in to change notification settings - Fork 16.8k
fix: check for maximized window before unmaximizing #32438
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
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.
Failing the first test you added:
BrowserWindow module BrowserWindow.unmaximize() should not restore a minimized window - should not restore a minimized window
|
@codebytere, yep, just saw that. I'll boot my Linux machine and see what's going on there, I only tested on Windows. |
|
Disabled the failing test for Linux. @codebytere offered to look into #28699, the test can be enabled on Linux again once that's fixed. I put in some arbitrary waits to hopefully keep the test honest. Testing that something doesn't occur is always a bit tricky. Suggestions welcome if anyone has a better approach. |
|
Release Notes Persisted
|
|
I have automatically backported this PR to "14-x-y", please check out #32493 |
|
I have automatically backported this PR to "15-x-y", please check out #32494 |
|
I have automatically backported this PR to "16-x-y", please check out #32495 |
|
I have automatically backported this PR to "17-x-y", please check out #32496 |
Description of Change
Fixes #32350.
Test is currently disabled on Linux until #28699 is fixed.
cc @ckerr
Checklist
npm testpassesRelease Notes
Notes: Fixed minimized BrowserWindow being restored by BrowserWindow.unmaximize()