[FLEX-34424] HierarchicalCollectionViewCursor.current returns null when previous sibling is removed

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Apache Flex 4.12.1
• Fix Version/s: Apache Flex 4.14.0
• Component/s: Advanced Data Grid, mx: Tree
• Assignee: Mihai Chira
• Reporter: Mihai Chira
• Created: 21/Jul/14 14:10
• Updated: 23/Mar/15 15:16
• Resolved: 21/Aug/14 09:35

Description

Steps to reproduce A: run HierarchicalCollectionViewCursor_FLEX_34424_Test - ideally with a previous version of HierarchicalCollectionViewCursor, HierarchicalCollectionView and LeafNodeCursor, to see how it fails.

Steps to reproduce B:

1. Create a HierarchicalCollectionView with a hierarchical structure with at least 2 levels of depth. See structure at the end of the ticket for example.
2. Create a HierarchicalCollectionViewCursor via HierarchicalCollectionView.createCursor().
3. Call HierarchicalCollectionViewCursor.seek(11), which (correctly) makes HierarchicalCollectionViewCursor.current == "Region(2) -> City(1) -> Company(2) -> Department(2) -> Employee(3)"
4. Remove "Region(2) -> City(1) -> Company(2) -> Department(2) -> Employee(1)" from its collection

Actual behaviour: HierarchicalCollectionViewCursor.current becomes null.
Desired behaviour: HierarchicalCollectionViewCursor.current stays "Region(2) -> City(1) -> Company(2) -> Department(2) -> Employee(3)".

Example structure:
Region(1)
Region(2)
Region(2) -> City(1)
Region(2) -> City(1) -> Company(1)
Region(2) -> City(1) -> Company(2)
Region(2) -> City(1) -> Company(2) -> Department(1)
Region(2) -> City(1) -> Company(2) -> Department(1) -> Employee(1)
Region(2) -> City(1) -> Company(2) -> Department(1) -> Employee(2)
Region(2) -> City(1) -> Company(2) -> Department(2)
Region(2) -> City(1) -> Company(2) -> Department(2) -> Employee(1)
Region(2) -> City(1) -> Company(2) -> Department(2) -> Employee(2)
Region(2) -> City(1) -> Company(2) -> Department(2) -> Employee(3)
Region(2) -> City(1) -> Company(2) -> Department(3)
Region(2) -> City(1) -> Company(2) -> Department(3) -> Employee(1)
Region(2) -> City(1) -> Company(2) -> Department(3) -> Employee(2)
Region(2) -> City(1) -> Company(2) -> Department(3) -> Employee(3)
Region(2) -> City(1) -> Company(2) -> Department(3) -> Employee(4)
Region(2) -> City(1) -> Company(3)

Issue Links

• is related to: FLEX-34458 HierarchicalCollectionViewCursor.current returns wrong item after previous sibling is removed when current was "${L}" (CursorBookmark.LAST)
• relates to: FLEX-34119 mx.collections.HierarchicalCollectionViewCursor causes CursorError RTE from ListCollectionView when the underlying collections change