Grid content with virtual scrollable disappears when changing to another tab/pane/view and back.

[Jyothi]

Hi,

Description - When I scroll to the middle of the grid on virtual scroll mode and move to another tab within app (DOM gets changed but component doesn’t destroy) and back, grid content is blank/disappears and scrollbar resets to top position.

[Zornitsa]

Hi Jyothi,

I configured an example implementing a Grid with virtual scrolling, initialized in a TabStrip, to try to reproduce the described behavior but to no avail:

• https://stackblitz.com/edit/angular-ovyrsf-42mwa8 

What I would suggest is making sure that the virtual scrolling of the Grid is configured correctly and meets all the requirements explained in the documentation article linked below:

• https://www.telerik.com/kendo-angular-ui/components/grid/scroll-modes/virtual/#toc-getting-started 

In case the virtualization is properly defined, it would be great if you could provide an example that replicates your scenario with the exact steps for reproducing the problematic behavior. This will help us track down the root of the experienced issue and provide further feedback on the case. 

I am looking forward to your reply.

Regards,
Zornitsa
Progress Telerik

[Jyothi]

Hi Zornitsa,

Thank you for getting back to me.

Came across this bug that someone else had reported. There is also a Stack blitz example regarding the grid virtualization scrolling.  Hope this helps you investigate further.

Content disappears on virtual mode inside SplitterComponent #3701

https://github.com/telerik/kendo-angular/issues/3701

Describe the bug
Grids content disappear and the scrollbar resets, after a new KendoSplitterPane is attached by *ngIf.

To Reproduce

1. Open the StackBlitz example https://stackblitz.com/edit/angular-xnswdx
2. Scroll about 100 entries (paging needs to be triggered)
3. Hit the "Hide/Show" button
4. Grids content disappear and the scrollbar resets.

Looking forward to hearing from you soon.

Regards,

Jyothi

 

[Zornitsa]

Hi Jyothi,

Thank you for referencing this bug report from our repository to clarify the experienced issue.

I want to inform you that considering your feedback, we have increased the priority of the bug in our backlog so it will move forward in our development queue. With that being said, I would suggest subscribing to the shared GitHub issue in order to receive updates on any changes in the status of its implementation.  

It is important to mention that in case your scenario differs from the one described in the bug report, I would like to ask you to describe the specific configuration on your side in the issue, so we would be able to consider it as well when we start fixing this bug.

We apologize for any inconvenience this issue may have caused. 

Regards,
Zornitsa
Progress Telerik