RadzenDropDown with AllowFiltering="true" and mobile devices

Hi,

We are upgrading one of our apps from version 4 to version 5, and we are struggling with the behavior of the DropDown box when having the filtering enabled and using a mobile device. The DropDown box is towards the bottom of the screen.

With Radzen version 4.20.1 everything works fine, you can select the DropDown box, the keyboard on the mobile device shows up over the DropDown box, but the DropDown box is scrolled towards the top of the screen to remain visible, and the focus is on the text box that is used to perform the filtering. Everything works wonderfully!

But when we use Radzen version 5.7.8, when the user selects the DropDown box, the keyboard on the mobile device shows up momentarily and also the search popup, but they both disappear right away. The keyboard is just momentarily displayed for a few milliseconds.

This is the code for the DropDown, it has nothing special:

 <RadzenDropDown Name="Host" FilterCaseSensitivity="FilterCaseSensitivity.CaseInsensitive" FilterOperator="StringFilterOperator.Contains" AllowFiltering="true"
                 Data=@ApplicationUsers TextProperty="FullName" ValueProperty="Id" AllowClear="true" @bind-Value=VisitRecord.HostUserID>
 </RadzenDropDown>

These are the screenshots when using version 4.20.1, the keyboard stays visible. But with the latest version the keyboard never stays visible, and the user cannot perform a search. We think the problem is related to how the focus is given to the textbox inside the DropDown box, but we haven't been able to pin point the actual problem.

For now we are disabling the filtering, but sometimes the users have to do a lot of scrolling.


Thanks in advance for your help!

Another test we have done with version 5.7.8, is setting the property OpenOnFocus="true". When we do this and the user select the DropDown box, the app seems to go into a infinite loop showing the keyboard, hiding the keyboard, showing the keyboard, etc. (very fast). I hope this helps.

By the way, this problem only seems to happen with Android phones (we have reproduced the problem with a Pixel with Android 15 and a Samsung Galaxy S22 Ultra with Android 14). We have tested with an iPhone 11, and we weren't able to reproduce the problem.

I was able to replicate and fix the problem - the fix will be released in our next update early next week.

1 Like

Thanks so much! Is there a workaround that I could apply in the meantime? Or the only option is to disable the allowfiltering for now?

There is no workaround however we will do our best to release the fix before the end of the day.

1 Like

Much appreciated! I find the Radzen Team is always very responsive. :sunglasses: