Skip to content
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: handle WM_GETMINMAXINFO instead of letting chromium do it #20000

Merged
merged 1 commit into from Aug 28, 2019

Conversation

brenca
Copy link
Contributor

@brenca brenca commented Aug 28, 2019

Backport of #19928

See that PR for details.

Notes: Fixed a bug where windows would sometimes shrink to 0 size after being restored on Windows.

* fix: remove WM_GETMINMAXINFO workaround since it's no longer needed

* fix: handle WM_GETMINMAXINFO ourselves

* fix: remove part of the chromium WM_GETMINMAXINFO handler
@ckerr ckerr merged commit 182f63d into 7-0-x Aug 28, 2019
@release-clerk
Copy link

release-clerk bot commented Aug 28, 2019

Release Notes Persisted

Fixed a bug where windows would sometimes shrink to 0 size after being restored on Windows.

@ckerr ckerr deleted the brenca/restore-after-minimize-7-0-x branch August 28, 2019 14:31
deepak1556 added a commit that referenced this pull request Nov 15, 2019
codebytere pushed a commit that referenced this pull request Nov 18, 2019
* Revert "fix: handle WM_GETMINMAXINFO instead of letting chromium do it (#19928) (#20000)"

This reverts commit 182f63d.

* fix: don't reset the width and height when correcting window placement
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
7-0-x backport This is a backport PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants