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
After #2193, anytime an outlined text box is not the default height (like with multiline text, or when a fixed height is set), the floating hint is not positioned correctly.
This screenshot is from the Fields page in the demo app, where the text box Height is set to 100.
Here is a gif of the same text box where I have removed the fixed height. All I'm doing is adding blank lines:
This is indeed a bug. But the problem isn't in the converter (but I also don't like the changes that were made to this converter, imo it's less readable now and there's more comments).
The problem resides in the MaterialDesignTheme.TextBox.xaml file. On line 241 and below you'll find following snippet:
The problem lies in the last Binding in the MultiBinding. When changing the Path property to Padding, the bug is fixed. I don't think the ActualHeight is needed to calculate the offset of the hint.
After #2193, anytime an outlined text box is not the default height (like with multiline text, or when a fixed height is set), the floating hint is not positioned correctly.
This screenshot is from the
Fields
page in the demo app, where the text boxHeight
is set to100
.Here is a gif of the same text box where I have removed the fixed height. All I'm doing is adding blank lines:
The issue seems to be due to the changes in
FloatingHintOffsetCalculationConverter
.The text was updated successfully, but these errors were encountered: