Hello,
in some cases there is no way to scroll grid using mousewheel. Try this REPL please - https://blazorrepl.telerik.com/GdkXuLuX10P8sOF040. Scroll down, focus any cell in the last row and try to scroll up using your mouse wheel again. Grid always scrolls back to the last row.
Can you check that please?
Very thanks.
Miroslav
I understand your point, but we do not know the total rows of the grid at the start they come from our server side, so therefore we use virtualization in all cases.
In any case, thank you very much, have a nice day.
The latest REPL is not a valid use case, because the total number of rows matches the page size and the scrolling does not meet the second bullet in my previous reply. In this case, there is no reason to use virtualization.
In any case, I agree that we should resolve this with higher priority.
Hello Dimo,
thank you for your answer and suggestions.
Unfortunately, the first one does not work generally - try please this modified REPL https://blazorrepl.telerik.com/GnONaiEr159jm1Qd13.
Moreover, it is difficult to set the smallest possible page size in our real app because the grid's dimensions are based on the current size of the browser itself. Sometimes the horizontal scrollbar can be visible, sometimes is not - when the user shrinks the viewport for instance, so the smallest page size can change dynamically...
We can revert to 4.4.0 but that is not a long term solution because we definitely want to enjoy the next versions.
So I would appreciate if that issue will be solved on your side.
Thank you for understanding.
Miroslav
Hi Miroslav,
Thanks for the runnable test page.
I think this issue is a side effect from the recent enhancement for keyboard navigation with virtual Grid scrolling.
What happens now is if there is a rendered focused cell outside the Grid viewport, then it will be scrolled into view. The ways to mitigate the problem are:
I am sorry if this is harming the user experience in your app. If the issue is a blocker, then you can revert to version 4.4.0.
I am converting this ticket to a public bug report and awarding you Telerik points for reporting it.
Regards,
Dimo
Progress Telerik