-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Resize our ContentDialog's when the window resizes #14722
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.
Well, I'll take it.
Hello @DHowett! Because this pull request has the Do note that I've been instructed to only help merge pull requests of this repository that have been opened for at least 8 hours, a condition that will be fulfilled in about 5 hours 51 minutes. No worries though, I will be back when the time is right! 😉 p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
Major thanks to @dongle-the-gadget in microsoft/microsoft-ui-xaml#3577 (comment) for coming up with this workaround. This PR will manually forward a `WM_SIZE` message to our `CoreWindow`, to trigger the `ContentDialog` to resize itself. We always closed these issues as dupes of the upstream one, so this doesn't actually close anything. HOWEVER, these are the following issues that reported this bug: - #2380 - #4463 - #5252 - #5810 - #6181 - #7113 - #7225 - #8245 - #8496 - #8643 - #9336 - #9563 - #5808 - #10351 - #10634 - #10995 - #11770 - #13796 (cherry picked from commit a4cf4e2) Service-Card-Id: 87727806 Service-Version: 1.17
🎉 Handy links: |
Major thanks to @dongle-the-gadget in microsoft/microsoft-ui-xaml#3577 (comment) for coming up with this workaround.
This PR will manually forward a
WM_SIZE
message to ourCoreWindow
, to trigger theContentDialog
to resize itself.We always closed these issues as dupes of the upstream one, so this doesn't actually close anything.
HOWEVER, these are the following issues that reported this bug: