[jira] [Created] (FLEX-34424) HierarchicalCollectionViewCursor.current returns null when last item of current level selected and previous sibling is removed

["Mihai Chira (JIRA)" <ji...@apache.org>]

Mihai Chira created FLEX-34424:
----------------------------------

             Summary: HierarchicalCollectionViewCursor.current returns null when last item of current level selected and previous sibling is removed
                 Key: FLEX-34424
                 URL: https://issues.apache.org/jira/browse/FLEX-34424
             Project: Apache Flex
          Issue Type: Bug
          Components: Advanced Data Grid, mx: Tree
    Affects Versions: Apache Flex 4.12.1
            Reporter: Mihai Chira
            Assignee: Mihai Chira


I'm about to commit a unit test which uncovers this bug. Until then, brief steps to reproduce:

# Create a HierarchicalCollectionView with a hierarchical structure with at least 2 levels of depth. See structure at the end of the ticket for example.
# Create a HierarchicalCollectionViewCursor via HierarchicalCollectionView.createCursor().
# Call HierarchicalCollectionViewCursor.seek(11), which makes  HierarchicalCollectionViewCursor.current == "Region(2)->City(1)->Company(2)->Department(2)->Employee(3)"
# 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)



--
This message was sent by Atlassian JIRA
(v6.2#6252)