[table]: TableSelection select all checkbox value is wrongly set when filtering data

[rvsia]

Bug Description

When filtering data in table and using select all checkbox to select all data, it's value status (checked/unchecked) gets unsynchronized with the data and it leads to un-expected behavior

Affected Component

ui5 table

Expected Behaviour

Select all checkbox is checked only if all data in the table are selected

Ideally it would great if the table selection would be controlled so we can manually set its value

Isolated Example

n/a

Steps to Reproduce

1. Filter data in table
2. Select all
3. Un-filter data
4. Select all checkbox is still checked

Log Output, Stack Trace or Screenshots

Priority

Medium

UI5 Web Components Version

Latest

Browser

Chrome

Operating System

MacOS

Additional Context

No response

Organization

SAP Signavio

Declaration

• I’m not disclosing any internal or sensitive information.

[didip1000]

Hey @rvsia,

Can you please provide an isolated example replicating the issue? You can edit one of our existing samples, or create one on https://stackblitz.com/.

Thank you,
Diana

[rvsia]

@didip1000 Can I provide a React example?

[didip1000]

Hey @rvsia,

If you can provide an example without react that would be preferable because we need to make sure the issue is with the components themselves not the react wrapper.

Thanks,
Diana

[nnaydenow]

Hi,

The behavior of the table seems to require clarification before confirming it as a bug.

What should happen if the "Select All" checkbox is clicked, and new items are added to the table? As I see it, the app currently has no way to understand that the checkbox was previously clicked in order to update its state accordingly.

@aborjinik what’s your opinion? Should we provide an event developers, allowing developers to align their model with the current component state? Or should we automatically uncheck the "Select All" checkbox when a new, unselected row is added to the table?

[Ankitadoshi]

Hi Team,

We are also facing the same issue in our SF project while filtering the table with multi select option
This is a high priority issue for us as our monthly release is impacted by this

Thanks,
Ankita