[
https://issues.apache.org/jira/browse/FLEX-17452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean updated FLEX-17452:
---------------------------------
Labels: easytest (was: )
> Combobox does not fully unregister when switching dataProviders
> ---------------------------------------------------------------
>
> Key: FLEX-17452
> URL: https://issues.apache.org/jira/browse/FLEX-17452
> Project: Apache Flex
> Issue Type: Bug
> Components: mx: ComboBox
> Affects Versions: Adobe Flex SDK 3.2 (Release)
> Environment: Affected OS(s): All OS Platforms
> Language Found: English
> Reporter: Adobe JIRA
> Labels: easytest
>
> Steps to reproduce:
> 1. Run the attached combobox.mxml application.
> 2. Click the "change" button.
>
> Actual Results:
> The combobox changes from showing "b" to "a" Additionally, the following
> trace lines are output:
> before change:
> c1.selectedIndex: 1
> c1.selectedItem: b
> after change:
> c1.selectedIndex: 0
> c1.selectedItem: b
> Expected Results:
> No visible change. d1 is no longer assigned to the combobox's dataProvider
> property. Changes to d1 should have no effect on the combobox.
>
>
> Workaround (if any):
> None.
> Notes:
> If you uncomment the array version and comment out the ArrayCollection
> version, it works fine. It appears that combobox is registering for
> ArrayCollection events on its dataProvider and is not unregistering them when
> the dataProvider is changed.
>
> Workaround:
> Subclass ComboBox, overriding the setter for dataProvider. Before calling
> inherited, unregister the collectionChangeHandler from the old dataProvider.
> See attached ComboBoxExt.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
