[
https://issues.apache.org/jira/browse/FLEX-34101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13908378#comment-13908378
]
Peter Hall edited comment on FLEX-34101 at 2/21/14 2:41 PM:
------------------------------------------------------------
We've run into the same issue, which appears to be caused by a change in how
CollectionEvents are dispatched when a collection is sorted.
Previously, when a property change causes an item to not match the filter, the
collection would dispatch a CollectionEvent with kind "remove". Since 4.10 the
event will have kind "update". DataGroup is not notified that the item has been
removed and gets into an inconsistent state.
was (Author: peterjoel):
We've run into the same issue, which appears to be caused by a change in how
CollectionEvents are distpatched when a collection is sorted.
Previously, when a property change causes an item to not match the filter, the
collection would dispatch a CollectionEvent with kind "remove". Since 4.10 the
event will have kind "update". DataGroup is not notififed that the item has
been removed and gets into an inconsistent state.
> Regression from 4.8 to 4.10: Spark list doesn't refresh with filterFunction
> ---------------------------------------------------------------------------
>
> Key: FLEX-34101
> URL: https://issues.apache.org/jira/browse/FLEX-34101
> Project: Apache Flex
> Issue Type: Bug
> Components: Spark: List
> Affects Versions: Apache Flex 4.10.0
> Reporter: Tristan
> Priority: Critical
> Attachments: Test.fxp
>
>
> I will post a project to test the case.
> To reproduce
> - open and launch the projet
> - click on one line
> - on the new View, clic on the only button
> Apache Flex 4.8:
> - the view is popped and the item clicked disappears
> Apache Flex 4.10
> - the view is popped and the item clicked doesn't disappears
> - Just scroll a little bit on the spark list and the item disappears
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
