Tree/TreeSelect Selection Propagation not working correctly with filter applied #16469
Labels
Status: Needs Triage
Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Describe the bug
Selection propagation in the treeview (and treeselect) only occur with filtered nodes and affects child selections based on parent selections and parent selection state (full or partially selected) based on child selections.
Environment
Angular, NodeJS & VS Code for development, C# .NET Core backendend
Reproducer
No response
Angular version
18.2.2
PrimeNG version
17.18.9
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
20.16
Browser(s)
Chrome,Edge (both latest version)
Steps to reproduce the behavior
Associated Stackblitz: https://stackblitz.com/edit/gnvdu7-7zrhrz?file=package.json
Both scenarios below are using a treeview or treeSelect component, filtering enabled, and selection propagation enabled.
Using the referenced stackblitz above where the node structure follows:
Scenario 1 - Parent does not select all children
Scenario 2 - Parent not reflecting child node selections
Other information: The following issue looks to be very similar to what I have reported: #15776
Expected behavior
Our experience prior to 16.9.6 with selection propagation was that the selections (or deselections) would occur regardless of filter and the parent properly reflects child selections regardless of filter.
The text was updated successfully, but these errors were encountered: