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
When placing a TextBox control within an Expandable.Header, the space key input is captured by the Expandable Control. This causes the Expandable control to unexpectedly collapse or uncollapse instead of inserting a space character in the TextBox.
To Reproduce
Create a new Avalonia application
Add an Expandable control to your XAML
Place a TextBox control within the Expandable.Header
Run the application
Click on the TextBox to focus it
Try to type a space character
Expected behavior
The space character should be inserted into the TextBox without affecting the Expandable control's state.
Actual Behavior
The space key input causes the Expandable control to collapse or uncollapse, and no space character is inserted into the TextBox.
Avalonia version
11.1.3
OS
Windows
Additional context
A workaround can been implemented by placing the TextBox inside the Expandable content and binding its value to a TextBlock in the header. However, this is not an ideal solution and complicates the UI structure.
This issue is particularly problematic when trying to provide descriptive names for UI elements that end users can edit. The current behavior significantly hampers usability and creates a counter-intuitive user experience.
The text was updated successfully, but these errors were encountered:
Description
When placing a TextBox control within an Expandable.Header, the space key input is captured by the Expandable Control. This causes the Expandable control to unexpectedly collapse or uncollapse instead of inserting a space character in the TextBox.
To Reproduce
Expected behavior
The space character should be inserted into the TextBox without affecting the Expandable control's state.
Actual Behavior
The space key input causes the Expandable control to collapse or uncollapse, and no space character is inserted into the TextBox.
Avalonia version
11.1.3
OS
Windows
Additional context
A workaround can been implemented by placing the TextBox inside the Expandable content and binding its value to a TextBlock in the header. However, this is not an ideal solution and complicates the UI structure.
This issue is particularly problematic when trying to provide descriptive names for UI elements that end users can edit. The current behavior significantly hampers usability and creates a counter-intuitive user experience.
The text was updated successfully, but these errors were encountered: