You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've found two issues with the Fluent2 TextBox that make it almost unusable. Note I'm running a custom build of the theme in .NET Framework 4.8 for legacy reasons so that may influence some of these results (that's why I'm ignoring that the ClearText button doesn't work at all).
The TextBoxClearButton does NOT stay right-aligned as it should (or left-aligned if RTL language). Also, please review WinUI as I'm not sure the clear button should EVER be below multi-line text. I suspect it always stays Top-aligned following the first line. Bottom line, the positioning of this button is completely wrong.
In order to select all text in a TextBox by clicking/dragging the user has to selected EXACTLY where the text starts/ends rather than anywhere in the TextBox. I suspect the TestPresenter is stretching to the proper size here.
Reproduction Steps
See below, it works in any Fluent2 TextBox:
Bad Clear Text Button position/alignment
Poor selection
Expected behavior
See WinUI3 gallery
Actual behavior
See above
Regression?
No response
Known Workarounds
No response
Impact
No response
Configuration
No response
Other information
No response
The text was updated successfully, but these errors were encountered:
Description
I've found two issues with the Fluent2 TextBox that make it almost unusable. Note I'm running a custom build of the theme in .NET Framework 4.8 for legacy reasons so that may influence some of these results (that's why I'm ignoring that the ClearText button doesn't work at all).
Reproduction Steps
See below, it works in any Fluent2 TextBox:
Bad Clear Text Button position/alignment
Poor selection
Expected behavior
See WinUI3 gallery
Actual behavior
See above
Regression?
No response
Known Workarounds
No response
Impact
No response
Configuration
No response
Other information
No response
The text was updated successfully, but these errors were encountered: