[Grid] Hiding or locking column scrolls to the position of the Grid

[yanmariomenev]

Describe the bug When hiding a column will cause the page to scroll to the Grid position. The issue is related to v5.0.1 ( kb-nav: content is scrolled to the top when focusing a header cell ). Locking the column will also focus on the last header cell and scroll the Grid horizontally (reference 1573208).

To Reproduce Steps to reproduce the behavior:

1. open - https://stackblitz.com/edit/angular-uvszf5-fi8sx5?file=app%2Fapp.component.ts
2. Press the hide column button

Expected behavior Not losing focus and scrolling the Grid position

Workaround The scroll can be disabled and re-enabled when pressing the button: https://stackblitz.com/edit/angular-uvszf5-jvbxlm?file=app%2Fapp.component.ts

A second workaround that keeps the horizontal scroll position of the Grid: https://stackblitz.com/edit/angular-7xgsx2-jkc1wm?file=src/app/app.component.ts

[dtopalov]

Seems related to https://github.com/telerik/kendo-angular/issues/3392

[yanmariomenev]

Also applies when the Grid is hidden and shown with ngIf - https://stackblitz.com/edit/angular-q3y33c-ez6cfq?file=app/app.component.ts ref - 1544866 The workaround can be also applied in this case.

[mbechev]

Similar behavior is reproduced when scrolling the Grid Column Menu almost out of view. Opening the popup scrolls the page:

https://stackblitz.com/edit/angular-pkwzx1?file=src%2Fapp%2Fapp.component.ts

1. Scroll the page to a similar state as shown on the screenshot.
2. Open the Column Menu

The workarounds suggested by Yanmario are still valid. Here is the second approach integrated in the demo: https://stackblitz.com/edit/angular-giwpmy?file=src%2Fapp%2Fapp.component.ts,src%2Fapp%2Fproducts.ts

[Kir4n]

Workaround is to set the column width to 0 or 1 (in case of virtual column) when hidden flag is turned on. Might be slow for grid with huge number of columns and rows.

[CheetahDev]

Hi,

We are using a workaround provided by the support for almost 2 years now.

Is there a plan to finally fix the issue? Latest support answer was stating "I also want to add that we recently increased the priority for fixing the issue, but we cannot provide any specific ETA at this time." but well, 2 years after it seems that the issue felt under the radar...

Any update would be appreciated!

Regards

[dtopalov]

Hello @CheetahDev,

I would like to assure you that no issue in this repo falls under the radar, but rather all of them get triaged, and listed in our backlog sorted in descending order by their evaluated priority. The estimated severity and frequency of the issue, as well as the presence of an workaround, and other considerations, are factored in.

I understand that not fixing a given issue for a certain period of time might be frustrating to affected developers and users, but we also operate with a limited resource available while we need to balance between developing, supporting and maintaining the product, so we are prioritizing accordingly.

Thank you for the understanding.

[dtopalov]

Fixed in v. 13.4.0