Fixes
- If a user ended a drag extremely quickly it was possible to lock the drag. This would need to be done faster than one
setTimeout. This was possible with a well performed force swipe interaction on mobile. This exposed a hole in how we performed lifting. The algorithm for lifting has been simplified and is now subject to testing to ensure that early exists are handled correctly. #172 - Dragging in nested lists on mobile is now fixed. Previously dragging an inner
Draggablewould actually lift the outer one on android #175. Thanks for raising this @ThomasJuster!