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: fire show event when BrowserWindow shown via maximize() #32979
Conversation
90aba1f
to
659d2df
Compare
Looks like the Windows builds unfortunately failed because they hit a 120 minute build time limit. |
Release Notes Persisted
|
I have automatically backported this PR to "16-x-y", please check out #33212 |
I have automatically backported this PR to "17-x-y", please check out #33213 |
I have automatically backported this PR to "18-x-y", please check out #33214 |
Description of Change
Fixes #32976.
This doesn't fix macOS (see #32947), only Windows and Linux, but the test will ensure that it works on macOS as well once that issue is closed.
This is somewhat of a half measure to address this particular case, instead of a holistic sweep to ensure 'show' is fired any time a BrowserWindow transitions from unshown to shown. I think that would be a good thing to do, but I don't have the bandwidth to do that at the moment (this is like, the 3rd issue in a chain of blocking issues), so this will serve as an incremental step in that direction which also adds test coverage.
Checklist
npm test
passesRelease Notes
Notes: Fire 'show' event when a BrowserWindow is shown via maximize()