You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pinning a root record changes summary result which means the summary pipe probably doesn't work correctly with pinned records
Export to csv exports pinned records with empty values
IMO filtered out rows that appear only because they are related to filtered in rows should not show they are pinned (because their pinned counterparts are not there Treegrid Pinned Row & Filtering #7172
TreeGrid does not retain the order in which the rows are pinned but instead applies the original order from the data source to the pinned area. For example if you pin the second row and then first one, the pinned rows should be in order [2, 1], but are instead in order [1, 2]. - Fixes Wrong Order of Pinned Records in Treegrid #7216
Search - Result item count is incorrect if a row that does not have matching results is pinned. Can be reproduced by searching by an unique value that exist in just 1 row and then pinning some other unrelated row. The count is 2, however only 1 match exists. - feat(igxGrid): Update navigation to include ghost rows. #7148
Search - Result item count is incorrect (doubled) and navigation between matches does not work if a row is pinned. - feat(igxGrid): Update navigation to include ghost rows. #7148
Can be reproduced by searching by a value that exists once in every row, observe the matches count, then clear search and pin any row and apply same search value and observe that now the match count is doubled. Nothing seems to be marked as active when you use findNext/findPrev.
Can be reproduced by searching by a value that exists once in every row, observe the matches count, then clear search and pin any row and apply same search value and observe that now the match count is doubled. Nothing seems to be marked as active when you use findNext/findPrev.
The text was updated successfully, but these errors were encountered: