[FLEX-20013] CLONE -AIR: dragDrop event is sent too early when using the NativeDragManagerImpl

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: Adobe Flex SDK 3.0 (Release)
• Component/s: Drag and Drop
• Environment: Affected OS(s): All OS Platforms; Language Found: English
• Assignee: Unassigned
• Reporter: Adobe JIRA
• Created: 27/Jun/09 10:51
• Updated: 27/Jun/09 10:51

Description

Steps to reproduce:
1. Import the attached project to FB.
2. Debug the AIR Application and view the console.
3.Mouse down on the Image in the Canvas and drag the item to a new location and release the mouse.
4. Note the trace output. It will look something like:
[SWF] dragImageCustom.swf - 785,310 bytes after decompression
target1.mouseX: 40, xOff: 39
target1.mouseY: 52, xOff: 39
mouseX: 268
5. In the AIR Application, change the WindowedApplication to an <mx:Application>. This should cause the Application to use the original Flex DragManager implementation. Debug the Application.
6. Repeat step #3 dragging the item to a similar location on the Canvas.
7. Notice the console. It will look something like this:
[SWF] dragImageCustom.swf - 601,043 bytes after decompression
target1.mouseX: 233, xOff: 42
target1.mouseY: 160, xOff: 42

Actual Results: There are a couple of major differences when using the AIR implementation of the DragManager vs the Flex original implementation of the DragManagaer:
1) The mouseUp event is triggered when you drag and drop an item using the AIR implementation.
2) In the AIR implementation of DragManager, the Canvas that you dropped the item on did not update its mouseX and mouseY property before the dragDrop event fired.

Expected Results: The Canvas's mouseX and mouseY properties should update before the dragDrop event fires. Also, the mouseUp event shouldn't get fired.

Workaround (if any):