[
https://issues.apache.org/jira/browse/FLEX-34229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Harui resolved FLEX-34229.
-------------------------------
Resolution: Fixed
Fix Version/s: (was: Apache Flex 4.13.0)
Apache Flex 4.12.1
Patch applied in fd4a17b5acbb732f239c33c09984cc429623c69d
> DataGridEditor doesn't remove the Event.DEACTIVATE listener on
> destroyItemEditor()
> ----------------------------------------------------------------------------------
>
> Key: FLEX-34229
> URL: https://issues.apache.org/jira/browse/FLEX-34229
> Project: Apache Flex
> Issue Type: Bug
> Components: Spark: DataGrid
> Affects Versions: Apache Flex 4.12.0
> Reporter: Mihai Chira
> Assignee: Alex Harui
> Fix For: Apache Flex 4.12.1
>
> Attachments: FLEX-34229.patch, _editorDeactivateHandler.fxp
>
>
> Steps to reproduce:
> 1. Import and run attached project.
> 2. Set a breakpoint in DataGridEditor.deactivateHandler().
> 3. Double click on 'hello' to show the editor.
> 4. Click in the grid under 'hello' to remove the editor.
> 5. Click on the Remove Grid button.
> 6. Click anywhere outside the AIR app to de-focus it.
>
> Actual result: the breakpoint is triggered, which means that the
> DataGridEditor is still responding to Event.DEACTIVATE even after the editor
> was closed, and even after the grid was removed.
> Desired result: DataGridEditor.deactivateHandler() should only be called
> while an editor is open, as long as the grid itself is still on stage (NB the
> grid can be removed while the editor is still open, see FLEX-34216 for the
> problems that causes).
> Expected result: the breakpoint is not triggered.
> Notes:
> -the second line of DataGridEditor.destroyItemEditor() looks like a typo:
> instead of addEventListener shouldn't it say removeEventListener(...)?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
