-
Notifications
You must be signed in to change notification settings - Fork 692
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
TextBox PlaceholderText is no longer centered correctly in v1.6.0 #10014
Comments
Not fixed. |
Does anyone even care? This breaks the whole styling and makes the app look ugly now. |
Unfortunately not. Are you too on Windows 10? |
Yeah, I'm still on Windows 10. I tested it on a Windows 11 machine, and it works fine there, so it seems to be an issue only affecting Windows 10 machines. |
Thought so... |
I'm having the same problem with TextBlocks, also on Windows 10. I'm currently working around it by changing LineHeight and LineStackingStrategy:
It's a hassle though. TextBox, CheckBox etc are harder because the TextBlock is nested. The entire template will need to be duplicated. You can find the original source in .nuget\packages\microsoft.windowsappsdk\1.6.240923002\lib\uap10.0\Microsoft.UI\Themes\generic.xaml |
I guess we can agree that changing and duplicating whole templates, to fix a bug that 1.6.0 introduced is a no-go. |
WindowsAppSDK 1.7.241114004-experimental1 also seems to have the same issue. So it is still not fixed in 1.7. |
Describe the bug
In WindowsAppSDK 1.5
<PackageReference Include="Microsoft.WindowsAppSDK" Version="1.5.240802000" />
it looks correct like this:In v1.6
<PackageReference Include="Microsoft.WindowsAppSDK" Version="1.6.240829007" />
it suddenly looks like this:So whatever has changed it messes with the positioning of the PlaceholderText.
Steps to reproduce the bug
Expected behavior
No response
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.6.0: 1.6.240829007
Windows version
Windows 10 (21H2): Build 19044
Additional context
No response
The text was updated successfully, but these errors were encountered: