Hi Kacper,

Thank you for sharing your opinion. We highly value it.

I confirm that even a slight scroll triggers a change in scope, altering the context even if the visual difference may not be substantial. It's important to note that the component can't predict where your scroll will conclude; it simply recognizes your intent to load the items above. Consequently, the DropDownList must invoke the OnRead function to accurately fetch the data.

Should any feasible methods arise for improving this behavior in the future, there's always the option to reconsider the status of this item.

Regards,
Hristian Stefanov
Progress Telerik

Hi Kacper,

I have conducted a thorough review of the information you shared and have taken the time to test the OnRead functionality on my own machine. As a result, I am ready to provide insights and relay my observations on the situation.

In this particular scenario, the behavior you described is as expected. This behavior occurs because, when you scroll down to the last element and then make a swift upward scroll, the page above attempts to load, and subsequently, making a rapid downward scroll initiates the immediate loading of the lower page. These actions lead to the event being called twice.

If we can assist with more information, I would be glad.

Regards,
Hristian Stefanov
Progress Telerik