-
Notifications
You must be signed in to change notification settings - Fork 716
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
FontIcon and SymbolIcon has weird padding on Windows 10 #9104
Comments
Shows fine for me on W10 Build 19045.3693:
Your version of Windows has been unsupported for 2-3 years now. https://learn.microsoft.com/en-us/lifecycle/products/windows-10-home-and-pro https://learn.microsoft.com/en-us/lifecycle/products/windows-10-enterprise-and-education |
I am aware of this. But since WinUI3 is labeled support down to 17763, I need to ensure the compatibility to the lowest version I want to support. So I want to know if this issue comes from the |
Will share this info with the font team. |
I'm gonna take a quick, wild guess and say this is caused by old OS, or maybe old version of .NET or framework or something like that. Also, I know that SymbolIcon (used to?) uses MDL2 and deprecated icon codes. See #6409 and MicrosoftDocs/winrt-api#2363. I'll have to search to see if Microsoft has fixed this recently... |
Thanks for reporting this. Since the target version of Windows has been out-of-support for years now, this bug is out-of-scope for the focus of the team. |
Describe the bug
FontIcon
andSymbolIcon
has weird padding that makes it offset to its center in its container. And this issue only seems to happen on Windows 10 with WinUI3, not with WinUI2.Steps to reproduce the bug
You got

You got
.
In UWP with WinUI2, with the same xaml, the result it expected.

Expected behavior
No response
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.4.2: 1.4.231008000
Windows version
Windows 10 (1809): Build 17763
Additional context
This issue is so universal, that it also bugged WinUI3 Gallery.

The text was updated successfully, but these errors were encountered: