Describe the bug
When a UWP/WinUI application is snapped to one side (in desktop or tablet mode), the upper part of its window is cut off.
Steps to reproduce the bug
Steps to reproduce the behavior:
Expected behavior
Screenshots
Version Info
NuGet package version:
This template needs to be updated to include the most recent released Windows version...
| Windows 10 version | Saw the problem? |
| :--------------------------------- | :-------------------- |
| Insider Build (xxxxx) | |
| October 2019 Update (18363) | Yes |
| October 2018 Update (17763) | |
| April 2018 Update (17134) | |
| Fall Creators Update (16299) | |
| Creators Update (15063) | |
| Device form factor | Saw the problem? |
| :-------------------- | :------------------- |
| Desktop | Yes |
| Mobile | |
| Xbox | |
| Surface Hub | |
| IoT | |
Additional context
Can't be reproduced.
You'd need to provide screenshots and detailed information about your display hardware/settings/configuration to get anywhere with this.
Screenshot of Microsoft Edge when maximized:
Window snapped to the left with Win+Left shortcut:
I can see this issue on a Surface Go (1820x1200 Resolution, 150% scaling) and on a Desktop PC (4k resolution, 200% scaling), both running Windows 1909.
There must be some edge-case, non-standard setting or software on both systems. Otherwise it'd be easy to repro and heavily reported by now. Try logging into Safe Mode or a different user account to see how it appears there.
The Windows Sandbox shows it working fine:
Can't be reproduced.
You'd need to provide screenshots and detailed information about your display hardware/settings/configuration to get anywhere with this.
Easy to reproduce. Enter Tablet Mode. (All of these are at 100% Scaling.)
This is how the Store looks on launch.
This how Store should look.
@shaheedmalik
The OP clearly stated:
When a UWP/WinUI application is snapped to one side (in desktop or tablet mode)
It is not reproducible in desktop mode on any of my devices.
If it only repros in tablet mode then that is an important detail and the issue should be corrected, including the title.
I tested it again on another machine (with a completely unrelated non-microsoft user account) and see the same issue. All machines are on build 18363.476 and I can reproduce it in desktop and tablet mode.
If anyone outside of @lhak can repro this in a normal Windows desktop environment, then please let us know.
Until then this is the difference between an issue impacting:
It's easily reproducible in both modes.
Open window in desktop mode. Win+Up, Win+Left
All 100% Scale.
So if you specifically:
Then the issue can be repro'd (and goes away if you hit Win+L/R again). Maximizing first wasn't part of the original steps.
However, this happens to all windows, not just UWP/WinUI ones. So this is a Windows 10 issue that belongs in the Feedback Hub, rather than something that should be addressed here. @lhak
@shaheedmalik Thanks for the double downvotes btw!
So if you specifically:
- First maximize a window
- Then hit Win+Left/Right to snap the window
Then the issue can be repro'd (and goes away if you hit Win+L/R again). Maximizing first wasn't part of the original steps.
However, this happens to all windows, not just UWP/WinUI ones. So this is a Windows 10 issue that belongs in the Feedback Hub, rather than something that should be addressed here. @lhak
@shaheedmalik Thanks for the double downvotes btw!
You're welcome!
The issue also occurs when you snap a window at the the top of the screen (via mouse) to maximize it.
@lhak thank you for opening this issue. As @kmgallahan pointed out, the problem isn't limited to UWP apps and won't be fixed in WinUI. Feedback Hub is definitely the best place for these types of issues, so please feel free to upvote the feedback I opened based on the information that was provided here.
Sorry to bump up this closed issue, but I can't seem to open your link for the feedback issue @YuliKl is there a Issue ID or smth I can search for? I'd like to vote for it because apparrently I'm one of the 800million users affected by this. Though I wouldn't have noticed without this issue.
Yulia's issue is internal and I don't know how to make it public. @jasonwurzel (or anyone) can you file a Feedback Hub item? I'll link it to the one @yulikl created.