List view with filter does not render properly

[Leomaradan]

Category

[ ] Enhancement

[X] Bug

[ ] Question

Version

Please specify what version of the library you are using: [1.12.0 ]

Expected

Select a value in the List View, type some text in the filter. If the item is hidden, the selection disapear and the selection event is triggered. If the item isn't hide by the filter, it remain selected

Observed Behavior

The selected item seems to be bound to the index of displayed items.

For exemple, if I select the item number 2 on the unfiltered listview, and I start to filter, the selection is shown on the new number 2 item, and the event for selection are not triggered. If I want to select the falsy-selected item, I have to click two-time on the element.

Steps to Reproduce

Put a list-view with item on a page
Add a trigger to check is the selection change
Typesome filter text

<ListView
items={this.props.items}
selection={this._getSelection}
selectionMode={SelectionMode.single}
showFilter={true}
></ListView>

[michaelmaillot]

Hi @Leomaradan,

In the latest version (3.15.0), the selected index is not bound to the index anymore:

However, if selection is outside the filtered data, it's not kept once filter reset. By now, it's the same behavior than the Fluent UI DetailsList component on which the ListView control relies.

Is it something required in On-Prem context only (which requests using version 1.x of the controls)? Or would you mind using latest version?

[ghost]

This issue has been automatically marked as stale because it has marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within next 7 days of this comment. Thank you for your contributions to SharePoint Developer activities.

[ghost]

Closing issue due no response from original author. If this issue is still occurring, please open a new issue with additional details. Notice that if you have included another related issue as additional comment on this, please open that also as separate issue, so that we can track it independently.