[MatSort] sort function doesn't render sorting arrow

[vadjs]

What is the expected behavior?

sort function in MatSort should update sorting arrow rendering state.

What is the current behavior?

Currently sort function in MatSort not updating sorting arrow rendering state.

What are the steps to reproduce?

https://stackblitz.com/edit/angular-cfcugl-17fxat
If you click "sort by name" button you will see this bug.
"Sort with fix" button shows the easiest way to fix this bug.

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

All

Is there anything else we should know?

[jysoo]

@jelbourn If no one is working on this, perhaps I can give it a go next weekend or so? :)

[jelbourn]

@jysoo go for it

[francescodist]

@jysoo The solution you proposed doesn't work properly for me, when the arrow is supposed to be cleared.
Calling the _handleClick() function, instead, solves it for me. Probably we could have a function on MatSort that basically does what "sortByNameFixed" is doing, provided an id (string) for a sortable

sortByNameFixed() {
    const sortHeader = this.sort.sortables.get('name');
    sortHeader['_handleClick']();
  }

[ovk]

Should MatSort also react to changes to active and direction properties and update sort header arrows state automatically to match the current state? This would be consistent with how paginator behaves.

[jysoo]

@jelbourn @andrewseguin May I ask if the team intends to incorporate a fix for this issue some time in the future? (There's a PR #16413) Thanks.

[rothsandro]

I just tested this again with Angular 13 and I cannot reproduce the bug anymore. I guess this has been fixed by some other changes. @vadjs Can you confirm that?

[viniciusschuelter]

I just tested this again with Angular 13 and I cannot reproduce the bug anymore. I guess this has been fixed by some other changes. @vadjs Can you confirm that?

i agree, the bug not happen anymore @jelbourn

[jelbourn]

Thanks for commenting- seems like this was incidentally fixed somewhere along the way. Feel free to reopen if someone can reproduce it still happening with a new version.