[
https://issues.apache.org/jira/browse/FLEX-35031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mihai Chira updated FLEX-35031:
-------------------------------
Description:
{{HierarchicalCollectionViewCursor.findAny()}} and
{{HierarchicalCollectionViewCursor.findLast()}} return true for any {{values}}
parameter that's a sealed class instance or the value {{null}}, even though
they don't actually find that item, and end up setting the cursor's {{current}}
property on the wrong item in the collection view.
I'm not sure if this causes bugs higher up the chain, but I imagine it does.
This bug has the same cause as FLEX-33058.
was:
{{HierarchicalCollectionViewCursor.findAny()}} and
{{HierarchicalCollectionViewCursor.findLast()}} return true for any value of
their {{values}} parameter that's a sealed class instance, even though they
don't actually find that item, and end up setting the cursor's {{current}}
property on the wrong item in the collection view.
I'm not sure if this causes bugs higher up the chain, but I imagine it does.
This bug has the same cause as FLEX-33058.
> HierarchicalCollectionViewCursor cannot find sealed class instance
> ------------------------------------------------------------------
>
> Key: FLEX-35031
> URL: https://issues.apache.org/jira/browse/FLEX-35031
> Project: Apache Flex
> Issue Type: Bug
> Components: Collections
> Affects Versions: Apache Flex 4.15.0
> Reporter: Mihai Chira
> Assignee: Mihai Chira
> Fix For: Apache Flex 4.16.0
>
>
> {{HierarchicalCollectionViewCursor.findAny()}} and
> {{HierarchicalCollectionViewCursor.findLast()}} return true for any
> {{values}} parameter that's a sealed class instance or the value {{null}},
> even though they don't actually find that item, and end up setting the
> cursor's {{current}} property on the wrong item in the collection view.
> I'm not sure if this causes bugs higher up the chain, but I imagine it does.
> This bug has the same cause as FLEX-33058.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
