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
We have previously raised this issue with Infragistics support who have provided an example of how we can override the logic that drives this and manage it ourselves. They also recommended that we raise an issue here aswell.
Description
We are having issues with the selecting multiple rows within the IgGrid. I have been able to replicate this in the online designer as well.
ignite-ui version: Ignite UI for jQuery 21.2.20212
change features>selecting>multipleSelection to true
select some rows in the grid using shift + down arrow key
click on a row
try and select rows using shift+up key or rows starting from above the ones from step 4
Result
The issue is that some rows are not highlighted properly on step 6
Expected result
The expected rows should be selected
Attachments
bandicam.2023-01-16.10-31-19-331.mp4
Interim solution
Temporary solution to override how ignite handles row selection (doesn't solve the problem but maybe could with some changes) as provided by Infragistics support
@benh500 You also need to enable the row selectors feature from the feature chooser and you can configure it to show/not show row numbering, checkboxes, etc.
Hi
We have previously raised this issue with Infragistics support who have provided an example of how we can override the logic that drives this and manage it ourselves. They also recommended that we raise an issue here aswell.
Description
We are having issues with the selecting multiple rows within the IgGrid. I have been able to replicate this in the online designer as well.
Steps to reproduce
Result
The issue is that some rows are not highlighted properly on step 6
Expected result
The expected rows should be selected
Attachments
bandicam.2023-01-16.10-31-19-331.mp4
Interim solution
Temporary solution to override how ignite handles row selection (doesn't solve the problem but maybe could with some changes) as provided by Infragistics support
Also see Example html file from Infragistics support
The text was updated successfully, but these errors were encountered: