Open NivedhithaV opened 7 years ago
the demo you refer to uses "multi" mode sort. (see below) I think if you use the default "single" mode sort it will behave with typical sort behaviour like you expect (clicking on second column header removes first selection).
I'm not sure I understand how or where multi mode sorting is used....
I'm not sure about the demo but I'm seeing similar issues in my app where I have the sortType set to single'
Okay. I was just looking at the demo that you pointed to for reproducing. You can easily fork one of the plunkers from other issues to demonstrate your particular problem without too much mucking around in plunker. My app seems to sort as expected in single mode but I have not tested thoroughly. I don't understand the purpose of multi unless perhaps there is grouping on the rows. There are a bunch of issues that relate to "refreshing" of the lists' source and the view not updating but those are ones where the list changes, not sorting.
I'm submitting a ... (check one with "x")
Current behavior Sorting works differently each time
Expected behavior
Reproduction of the problem Can be seen in demo - http://swimlane.github.io/ngx-datatable/#client-sorting Sample gif - https://gist.githubusercontent.com/NivedhithaV/d8b0a44961cf5b6611cbbeda161d335d/raw/d8aac582de49839a9c2ec45af6f8aaac4865f31c/swimlane.gif
What is the motivation / use case for changing the behavior? Better user experience
Please tell us about your environment: N/A
Table version: 0.8.x 9.3.0
Angular version: 2.0.x 4.0.0
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ] Chrome, havent tested in others
Language: [all | TypeScript X.X | ES6/7 | ES5] Typescript