Don't fire draggable:end if draggable:start has not been fired

[cdauth]

draggable:start is fired when the first mousemove happens after mousedown. Currently, draggable:end is fired on mouseup, regardless if there has been a mousemove. Thus, when clicking a draggable element (without moving the mouse between mousedown and mouseup), draggable:end is fired without draggable:start having been fired.

This has the effect that ng-drag-success is executed on the draggable element as if it had been successfully dropped somewhere, but in fact no droppable element will execute ng-drop-success, as droppable elements only start checking whether anything isTouching them after a draggable:start event.

In my case I am moving an element, so one is removed on ng-drag-success and another one is created on ng-drop-success. When clicking the element, it is removed.

[tafel]

I just bump again this PR, because it helps me too, with Chromium 47 on laptop. When I first drag the element, all is fine. Then, if I do a simple click on it, without any dragging, the drag-end event is called. This PR resolve this case too. Thanks in advance for merging!

[francoisgrogor]

Any reason why this has not been incorporated?