Hi, we are experiencing an issue where when using the down key to change which item is selected that the grid will start scrolling on its and does some wierd behavior.
I am trying to attach a sample project that shows this behavior but cant see how but i do have a sample project that can reproduce this 100%.
If you run the project and click into the 4th cell of the first row, then hit the down key 6 times the grid will start scrolling on its own. While the grid is scrolling on its own if you watch the Some Button down at the bottom it will move focus to the button at some point in time.
In this demo code i had to get the width and height just right to be able to 100% reproduce it but with the way we are using RowDetails and our styles it doesnt matter what the height and width are it always happens all the time.
We have found two things that fixes the issue, both are not options for us. If you disable RowVirtualization the issue goes away and if you dont use RowDetails the issue goes away.
This is currently a blocking issue for our product and are hoping to see if we can get some sort of hotfix that fixes this issue.
Thanks
I am trying to attach a sample project that shows this behavior but cant see how but i do have a sample project that can reproduce this 100%.
If you run the project and click into the 4th cell of the first row, then hit the down key 6 times the grid will start scrolling on its own. While the grid is scrolling on its own if you watch the Some Button down at the bottom it will move focus to the button at some point in time.
In this demo code i had to get the width and height just right to be able to 100% reproduce it but with the way we are using RowDetails and our styles it doesnt matter what the height and width are it always happens all the time.
We have found two things that fixes the issue, both are not options for us. If you disable RowVirtualization the issue goes away and if you dont use RowDetails the issue goes away.
This is currently a blocking issue for our product and are hoping to see if we can get some sort of hotfix that fixes this issue.
Thanks