The suggestions view won't disappear when the AutoCompleteView loses and receives focus and the entered text is quickly deleted.
The AutoCompleteView is not visible in the Accessibility tree.
Setting AutomationId to the control has no effect and the element cannot be accessed in a testing project.
Attached is a video of how to reproduce the problem on UWP.
Steps to repro
=> Observe the infinite loop.
Use the following code:
<StackLayout Orientation="Vertical">
<telerikInput:RadAutoCompleteView ItemsSource="{Binding Source}"
SuggestMode="SuggestAppend"
TextSearchPath="Name" />
<telerikInput:RadAutoCompleteView ItemsSource="{Binding Source}"
SuggestMode="SuggestAppend"
TextSearchPath="Name"/>
<telerikInput:RadAutoCompleteView ItemsSource="{Binding Source}"
SuggestMode="SuggestAppend"
TextSearchPath="Name"/>
</StackLayout>
Steps to reproduce:
Hello,
As per forum thread https://www.telerik.com/forums/autocompleteview-causes-memory-leaks ACV control causes memory leaks on iOS.
Here is the repro project https://github.com/VitalyKnyazev/AutoCompleteViewLeak
Thanks
Vitaly
When the control is hosted inside RadPopup, the application crashes. This is due to the fact that nesting popups is not supported.
Consider changing the implementation of the RadAutoCompleteView to use different control for visualizing suggestions and NoResults message.
I have an autocomplete that needs to fire some validations even when the user does not select anything from the suggestion view, i.e when the autocomplete Loses the Focus.
I saw that "Completed" event is in development, but that is not enough for me, I would need the "Unfocused" event.
Provide an API for changing the SuggestionView position. For example the SuggestionView could be visualized above or under the input control.
Setting the FontSize property of the AutoCompleteView control to anything larger than 20 badly clips the text of both watermark and selected/written text, at least on iOS. I've tried various "hacks" with increased control heights and/or padding, themes etc, but it doesn't matter, it still clips.
Seems to work fine using RadEntry for example, so it should really be the same with AutoComplete?
Reproducing is as obvious as setting the FontSize property.