This is preview!
We're not trying to prevent you from adding a click handler, and we aren't. But starting a distance 0 selection means no click will trigger. We're trying to provide a way for either of the events to occur but not both at the same time. Distance 0 means only the selecting events should, because selectable is greedy on mousedown with distance 0. Distance greater than 0 means selectable doesn't get involved until after at least one mousemove, meaning it doesn't get in the way of click or dblclick.But my understanding is that jQuery and jQuery UI should limit the way we do things as less as possible. So why prevent me from adding a click handler if I want to?
That's a fine example to discuss. The question is not whether a click should be allowed. The question is whether at the point of a click or dblclick there should also have occurred a selectstart and a selectstop. Our opinion is no, they shouldn't both happen. Either you're clicking/double-clicking or you're starting a selection. If you're clicking you're not clicking and starting and stopping a selection in place. Same thing with double click.I'll tell you my use case to get you a better understanding.
Imagine a file manager. You can select files and do stuff with them. But you can also just dblclick one file to do stuff with it ("execute" it). Setting a distance of greater than 0 just doesn't feel right. The user expects a certain behavior.