[Grid] [TreeList] undesired behavior when reordering columns and using virtual columns

[svetq]

Describe the bug When using virtual columns where some of them are grouped and can be reordered, then if you try to reorder the columns of a group the headers of the columns will be no longer proper.

To Reproduce Please see the following example: https://stackblitz.com/edit/angular-vyebsk-zknxs2?file=app/app.component.ts

Try to reorder the columns of a grouped column to observe the issue.

[prydzewski2]

Currently working workaround is to recreate grid or treelist in columnReorder callback method. I used ngIf and boolean flag which value I set to false and after 300ms timeout back to true

[gareth-ferretsoftware]

Not sure how great a workaround this is but to get around the issue we tweak the width of the column to force a change and then restore it.

  public onColumnReorder(event: ColumnReorderEvent): void {
    const columns = this.gridColumns.value;
    columns[event.newIndex].width += 1;
    this.gridColumns.next(columns);    
    setTimeout(() => {
      columns[event.newIndex].width -= 1;
      this.gridColumns.next(columns);
    });
  }

[ceby-gannetflemming]

We've been on a slow burn implementation of this grid. I wrote the code for it in November of 2020 but we didn't start testing it till April of 2021. The testers found this bug then but I haven't been back to fix it till now. Now I see that it's been open for almost a year. It would be nice to see this fixed but @gareth-ferretsoftware's workaround worked for me.

[flogy]

Having the same issue. Would be nice to have this fixed instead of having to use a workaround.

[flogy]

Still an issue in 11.3.0.

[karolkolodziej]

I also stumble upon this issue, any update? Workaround from @gareth-ferretsoftware works well for now thanks but Is that something that can be recommended or is there any other more robust workaround?

[irowbin]

Why this still is not fixed? We are using the latest version of kendo and I noticed the same and ended up commenting here.

[bm64]

Could someone provide us with updated status of the issue and hopefully ETA for the fix? @gareth-ferretsoftware workaround seems to work well, but I'd still like to see more robust workaround from the team. @tsvetomir perhaps you could take a look at the issue?

[tsvetomir]

The issue is not fixed yet, sorry! We're reviewing it and will post an update with an ETA.

[shivambindal93]

Hi Team, Let us know once the issue is fixed or is part of any planned release.