Hi,

We've noticed a significant difference in how the "Select All" checkbox functions in the Grid and TreeList when paging is enabled.

Our application uses both components, and users expect them to behave consistently. However, we’ve identified several issues:

1. Inconsistent User Expectations

• In the Grid, "Select All" applies only to the current page.

• In the TreeList, "Select All" applies to all pages, including hidden rows.

• This inconsistency can confuse users who switch between these components, leading to unexpected behavior and frustration.

2. Confusing Bulk Actions

• In the Grid, users understand that selections are limited to the visible page.

• In the TreeList, users might unknowingly select thousands of records, potentially causing unintended bulk updates or performance issues.

3. Risk of Data Loss or Errors

• Users assuming the TreeList behaves like the Grid might:

  • Select all rows, perform an action (e.g., delete or update), and unintentionally affect all pages instead of just the current one.

  • This can lead to accidental data loss or incorrect modifications.

We need a consistent approach to "Select All" behavior across both components to prevent confusion, errors, and performance issues.

Expected behavior

If "Select All" is checked, it should:

• Select all visible rows on the current page.
• Select all children of selected parents, even if those children are on other pages.
• Maintain selection when navigating to another page.

If it should be submitted as a bug, please let me know.