You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flex.apache.org by "Jan F. Weber (JIRA)" <ji...@apache.org> on 2014/07/17 08:42:04 UTC
[jira] [Updated] (FLEX-34406) Darg&Drop events fired in wrong order
on mobile
[ https://issues.apache.org/jira/browse/FLEX-34406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan F. Weber updated FLEX-34406:
--------------------------------
Attachment: DragDropBug_Mobile.fxp
Please find attached a simple example.
You will see traces like this:
onDragEnter dragTarget1
onDragEnter dragTarget2
onDragExit dragTarget1
onDragExit dragTarget2
onDragEnter dragTarget1
onDragEnter dragTarget2
onDragExit dragTarget1
onDragExit dragTarget2
[...]
This cleary shows the events being fired in wrong order.
> Darg&Drop events fired in wrong order on mobile
> -----------------------------------------------
>
> Key: FLEX-34406
> URL: https://issues.apache.org/jira/browse/FLEX-34406
> Project: Apache Flex
> Issue Type: Bug
> Components: Drag and Drop
> Affects Versions: Apache Flex 4.12.1
> Environment: Win7 64Bit, FB 4.7
> Reporter: Jan F. Weber
> Labels: DragManager, drag&drop
> Attachments: DragDropBug_Mobile.fxp
>
>
> When there are droptarget areas directly next to each other drag and drop events get fired in the wrong order:
> DragEvent.DRAG_ENTER gets fired before DragEvent.DRAG_EXIT.
> This happens when publishing for mobile platforms (this uses a different DragManager class asfaik). Desktop application handles the events in correct order.
--
This message was sent by Atlassian JIRA
(v6.2#6252)