Don't need a double arrow here.
Added a spec helper to DRY up the specification for the metadata object that gets passed to draggable/droppable event callbacks.
The start, drag, and stop callbacks of draggable now receive the helper's position through a metadata object. Returning false from the start or drag callbacks prevents/cancels the drag.
We should save the pointer-events property every time a drag is started.
The start, drag, and stop callbacks of draggable now receive the helper's offset through a metadata object.
The drag and stop callbacks of draggable now receive a reference to the helper element through a metadata object.
Modifying metadata.position in the drag callback now changes the actual position of the drag helper.
Synchronizing the appending of a synthesized helper with the invocation of the first drag handler.
Cancelling the start of a drag should also unhook the document's mousemove handlers.
Let's be a little bit more diligent when it comes to cleaning up after a drag event.
Call the drag handler immediately, following a drag start event. Every subsequent time, call it coincident with frames being ready to render.
Moved getEventMetadata() into the base class.
A droppable's over callback now receives the draggable, and the draggable's helper element, position, and offset.
Bringing the droppable's out callback spec in line with the others, stylistically.
This needn't be a double arrow.
A droppable's drop callback now receives the draggable, and the draggable's helper element, position, and offset.