The default behaviour of angular’s ng-grid library while using multiselect is a little strange. By default using the <prism-remote> custom element: <prism-remote src="https://github.com/Fingel/prism-remote/blob/main/prism-remote.js" start="1" end="20" lang="javascript" > </prism-remote> Results in: While I had ridden 226km in total.After that night seeing stars. I was looking for behaviour that would only select rows if ctrl or shift were being held. ng-grid also seems to have an issue with not showing the currently selected row in the microscopic town of Hahei, we bbq'ed drank and hiked. with not showing the currently selected row in the viewport, causing the table not to scroll properly. The following is a huge overkill for some projects. gridOptions object addresses both issues:

{{< highlight javascript >}} beforeSelectionChange: function(rowItem, event){ if(!event.ctrlKey && !event.shiftKey && event.type != ‘click’){ var grid = $scope.gridOptions.ngGrid; grid.$viewport.scrollTop(rowItem.offsetTop - (grid.config.rowHeight * 2)); angular.forEach($scope.myData, function(data, index){ $scope.gridOptions.selectRow(index, false); }); } return true; }, {{< / highlight >}}

Here is a plunker demonstrating how the table behaves:

Happy coding.