Issue: grid paging allows user to page next before the previous page requests data has returned causing unintentional behavior
Process to reproduce
- Bind data to a grid
- Start at index 1 and click “next page” 20 times
- The grid will navigate to the 20th page
- Data will load
- Wait and observe grid will continue to reload as each async call returns
- It will continue to process each result set and change the grid page without interaction from the user. If paging takes 3 seconds this process will continue for 1 minute. (3 seconds * 20 page requests) and the grid will page every 3 seconds for the next minute
• From the users perspective I assume the expectation is that they hit nextnon the paging control 20 times and once they arrive at the 20 th page the grid will remain at that index until further user interaction.
how can i prevent the user from making subsequent calls until the initial call has returned. does the grid have a feature to support this? that is keeping the grid page in sync with the actual data that is returned. for example the user should not be able to click next for the second time until the result set of the first call is returned, the grid is bound and paged