[MGNLUI-3002] Unselect items when you close a node in a tree Created: 13/Jun/14  Updated: 30/Nov/15  Resolved: 17/Sep/14

Status: Closed
Project: Magnolia UI
Component/s: tree/list
Affects Version/s: None
Fix Version/s: 5.3.4

Type: Bug Priority: Critical
Reporter: Andreas Weder Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: next, usability, ux
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File 1 selected items visible.png     PNG File 2 selected items invisible.png    
Issue Links:
dependency
relation
is related to MGNLUI-2789 Show the number of selected items to ... Closed
is related to MGNLUI-2756 Moving multiple pages via d&d just mo... Closed
is related to MGNLUI-2806 Show the total number of selected ite... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Release notes required:
Yes
Date of First Response:

 Description   

Please make sure that all currently selected child items of a parent node (and grandchild and grandgrandchild... items) are unselected once that parent node is closed.

The #selected items shown in any view, in particular the tree view, must always correspond to the number of visible, selected items (including those below the fold). But currently, if you close a single node in the tree, the items inside it remain selected. That's against this principle. When a node is closed, *all its currently selected child items should in fact get deselected.

If you have doubts that this should work like this, the following case might convince you. You have two items selected inside a parent node, then that node is closed. If those items remain selected, how are you going to know, where these items actually are? You would have to re-open every node and go looking for them.

That's why any operation affecting the selection of items (such as checking single items or selecting all items at once) only works on the set of currently visible items. Check that with tree implemenations you know (e.g. the Finder or Eclipse).



 Comments   
Comment by Andreas Weder [ 18/Jun/14 ]

Added two screenshots that illustrate the problem some more.

Comment by Federico Grilli [ 18/Jun/14 ]

IMHO, MGNLUI-2789 is related, in the sense that helped discovering the problem but it's not the cause which probably lies in TreeTable code

Generated at Mon Feb 12 09:02:15 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.