-
Notifications
You must be signed in to change notification settings - Fork 675
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
The control buttons and shadow of a window with custom title bar is so weird #7131
Comments
This still reproduces in Windows App SDK 1.1.1. Only difference between the two windows above is Ping @rkarman |
Thanks for the ping here @riverar, I was not aware of this issue being logged. @marb2000 / @MikeHillberg can one of you move this issue over to WinAppSDK so we can assign the proper owners and track this with the windowing team? |
Same behaviour observed for Windows App SDK 1.2.221116.1 |
@MikeHillberg @jonwis Can you assist here with a move to WAS repo? |
I think we're in the right place; this looks like Window.ExtendsContentIntoTitleBar. |
Unfortunately this isn’t solved yet in the latest WinAppSDK version. |
Ensure this is invoked after you (stumbled over this in WinUI Git Hub example)
|
Thank you very much!! I’ll try that later today :) |
The problem is still not fixed yet. |
BTW in WASDK 1.4, the control buttons issue has been fixed. |
closing as fixed in winappsdk 1.4 |
Describe the bug
This is how a window with default system title bar looks like:
This is how a window with
ExtendsContentIntoTitleBar=true
looks like:You can observe that the size (and the shape) of control buttons is not consistent:
Also, the depth of shadow of the window is not identical:
Steps to reproduce the bug
ExtendsContentIntoTitleBar
totrue
Expected behavior
The control buttons as well as shadow of the window should be identical both with system title bar and custom title bar.
NuGet package version
WinUI 3 - Windows App SDK 1.1 Preview 3: 1.1.0-preview3
Windows app type
Device form factor
Desktop
Windows version
Windows Insider Build (22621)
The text was updated successfully, but these errors were encountered: