-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
[Settings] Plugin search field: Text and symbol overlap #13080
Comments
Thanks for flagging, seems that this PR will fix it: microsoft/microsoft-ui-xaml#5779 Once this gets merged in we can update the WinUI package so the issue will resolve itself :)! |
@niels9001 |
Fixed in |
@niels9001 Please update the project. Thanks! |
The fix for this issue ended up being reverted in #15138 , due to including the WebView dependencies. A bit more investigation needs to be put here to understand the implications. |
Project |
@Jay-o-Way Windows Apps SDK apps (like PT Settings) still use WinUI 2.7 - the bug is fixed in 2.8, once that goes into WAS we can update and we can then close this issue :). I'll mark it as blocked for now. |
Oh, I thought we moved to WinUI3? |
Gotta love the naming :-). WinUI3 = app model/framework (that comes with the Windows Apps SDK) So WinUI 3 (the app model) uses WinUI 2.x components (e.g. UWP or XAML Islands) can use WinUI 2.7 to replace the default components. tl;dr; WinUI 3 (= Settings) still uses the 2.7 version of the UI components. Once 2.8 is out of prerelease, it will adopt 2.8 which contains the fix for this bug :). |
Ah yes that makes sense 😆 Maybe we can move to "pure" WinUI3 without XAML islands and such? |
We did with 0.58. Settings now uses WinUI3 (so no more XAML Islands), which depends on WinUI 2.7 for the control styles. We just need to wait for WinUI 3 to adopt WinUI 2.8 and update the package to get this bug fixed. |
Is this still an issue with the latest version? /needinfo I believe not :) |
no. it is fixed. thanks for reminding. |
Without cursor focus it looks this:
The text was updated successfully, but these errors were encountered: