I've noticed a problem with server filtering when the DropDownList is near the bottom of the page. To reproduce the problem, go to http://demos.telerik.com/aspnet-mvc/dropdownlist/serverfiltering , and shrink the browser window so that the bottom of the browser comes up to to the bottom of the box around the products dropdown. (See attached image for example.)
Click the products dropdown and notice the list is expanded above the control, which is good.
Now type "c", followed by "h". The list now moves below the control, off the page, and it can't be seen. I haven't found a way to be able to see the products in the filtered list, because if I click the scrollbar to try to scroll down the control loses focus and selects the current item, and the same happens if I try to use my mouse's scroll wheel. I am able to arrow down through the products, but it is still very awkward to not be able to see the list.
Also, this example is not a huge problem on this page, because the user could scroll the page down before entering the dropdown, and then be able to see all the contents. But in my app several pages have DropDownLists at the very bottom of the page, which makes it impossible to ever see the filtered list.
I think a good fix for this would be that if the DropDownList starts off expanded above the control, to force it to stay displaying above the control while filtering is taking place.
7 Answers, 1 is accepted
Hello Kevin,
Indeed, we are aware of this issue and it is logged in our bug tracking system. The fix will be available for download in some of the next internal Kendo UI builds.
Regards,Plamen Lazarov
Telerik
Plamen, thank you for this information. Can you give any estimate on when this might be fixed? Seeing the issue ranked as "Low" severity in GitHub concerns me that it might not be addressed very quickly. Since this affects so many different controls and makes autocomplete unusable when those controls are near the bottom of the page, it feels like it would warrant a higher severity to me.
Hello Kevin,
A fix may be included in the upcoming Q3 release which is scheduled for the end of September. But I am afraid that we can not commit to any deadlines for resolving the issue.
Regards,
Plamen Lazarov
Telerik
Plamen, can you please give an update on this bug? I see no updates in the issue on github, and it is still marked with low severity, which is very concerning to me as we are getting closer to our application launch
Interestingly, I see in this example that this bug was introduced in the 2015 Q2 update (2015.2.624). 2015 Q1 SP2 (2015.1.429) and previous releases worked correctly.
Hello Kevin,
In the last months we were focused on implementing the Spreadsheet, which is a huge development effort, and unfortunately influenced tasks with lower priority. Please accept my apologies for any inconvenience this may cause.
Plamen Lazarov
Telerik
Thank you, Plamen. What is the latest update on this bug? Are lower priority tasks being addressed now? If not, can this task bug be raised to a higher severity level? (It is still set to low in github.)
The fix is scheduled for Q1 2016 release. The issue priority was changed to "high".
Regards,
Georgi Krustev
Telerik