jsPlumb scope should not be assigned to elements made draggable using jsPlumb.draggable

[GoogleCodeExporter]

jsPlumb uses one internal method to initialise dragging for both Endpoints that 
users create and also for elements made draggable with jsPlumb.draggable(..). 
In the latter case, though, the user is not expecting jsPlumb to do that, and 
people get caught out when they have some droppable that jsPlumb fails to 
interact with.

so the solution seems to be that jsPlumb should not set its own scope when the 
user calls jsPlumb.draggable. if they supply one, great, let it be passed 
through.  but otherwise it should not be set.

Original issue reported on code.google.com by simon.po...@gmail.com on 25 May 2012 at 12:04

[GoogleCodeExporter]

fixed in 1.3.9.  this was only an issue for jquery and yui; mootools adapter 
was fine.

Original comment by simon.po...@gmail.com on 26 May 2012 at 7:14

• Changed state: Fixed