For touch devices, drag start should have a optional delay and cancelation threshold for moving.

[GoogleCodeExporter]

Currently the dnd library will drag soon as you touch the element that has been 
set to draggable. This prevents any type of scrolling to happen if draggable 
content is touched.

What is the expected output? What do you see instead?
The draggable element should be long pressed in order to drag (Maybe if it is 
within a element that is scrollable or optional delay).

Should also have something similar to getBehaviorDragStartSensitivity for 
canceling start drag while in the long press mode.

Original issue reported on code.google.com by ak...@tanoshi.net on 30 Jan 2012 at 7:38

[GoogleCodeExporter]

Making draggable widgets not respond immediately to touch breaks the sense of 
interactivity.

I suggest changing the application user interface so that there is a place for 
the user to drag/scroll the content, i.e. provide some whitespace or background 
area in the app where there are no draggable objects.

Original comment by fredsa@google.com on 28 Mar 2013 at 10:10

• Changed state: NotPlanned

[GoogleCodeExporter]

I think both suggestions (from  ak...@tanoshi.net and fredsa@google.com) make 
sense.

If you look at the todo list app Any.do, which is very well designed, the user 
touch the item approximatively one second, the item appearance change, and then 
the user is able to drag.

> I suggest changing the application user interface
I think this choice should be given to the client application of gwt-dnd.

Original comment by g.parame...@gmail.com on 7 Aug 2013 at 8:00