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 the suggestion list of an AutoSuggest box opens normally, it resets the scroll view so the first element is in view.
When the suggestion list opens upwards (due to not enough space below the element), it does not reset the scroll view to the first element in view.
This can be replicated in the WinUI 3 gallery.
Steps to reproduce the bug
In the WinUI 3 gallery, go to the AutoSuggestBox
Drag the Window to the bottom of the screen so the AutoSuggestBox is just above the bottom of the screen
Type a character (for example "a")
The Suggestion list opens up
Scroll a bit in the Suggestion list
Close the suggesiton list (for example by pressing enter)
Remove the typed character, the suggestion list opens up again but not scrolled to the start of the list.
Type another character, the suggestion list is still not scrolled to the start of the list
Expected behavior
The suggestion list is scrolled to the start of the list so the first item in the list is visible.
Screenshots
NuGet package version
WinUI 3 - Windows App SDK 1.6.3: 1.6.241114003
Windows version
Windows 11 (23H2): Build 22631
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
When the suggestion list of an AutoSuggest box opens normally, it resets the scroll view so the first element is in view.
When the suggestion list opens upwards (due to not enough space below the element), it does not reset the scroll view to the first element in view.
This can be replicated in the WinUI 3 gallery.
Steps to reproduce the bug
Expected behavior
The suggestion list is scrolled to the start of the list so the first item in the list is visible.
Screenshots
NuGet package version
WinUI 3 - Windows App SDK 1.6.3: 1.6.241114003
Windows version
Windows 11 (23H2): Build 22631
Additional context
No response
The text was updated successfully, but these errors were encountered: