Hareeshchandera / jsplumb

Automatically exported from code.google.com/p/jsplumb
0 stars 0 forks source link

endpoints can be dragged with jqueryUI #189

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
With the 1.3.4 I have a new issue. The endpoints can be dragged, which is wrong 
and was not a possibility in 1.3.3.

It can be seen on the demo page:
http://jsplumb.org/jquery/demo.html

- try drag the endpoint on the left of "window4"
===result===
1) the endpoints moves
2) we got the errors in the console:
jsPlumb function failed : TypeError: aZ.stopDrag is not a function
jquery...-min.js (line 1)
jsPlumb function failed : TypeError: bk.element is null
===expected=== 
the endpoint stays on the node.

- This is only a problem with jQuery and jQueryUI. Without  the jQueryUI lib, 
it works.
- this is not a problem with Mootools (as seen on the demo page)
- the problem is also with YUI3.
- this was not a problem with 1.3.3 and also no problem with 1.3.4-RC1 (found 
at http://morrisonpitt.com/jquery.jsPlumb-1.3.4-RC1-all.js)

Tested on: Firefox 9 and IE9. In both a problem.

So it clashes probably with jQueryUI, also I noticed (which can help resolving 
the issue)
- The SVG elements are in a <div>, first this was not the case?
- This <div> has the classes: ui-draggable and ui-droppable
Example:

<div class="_jsPlumb_endpoint ui-draggable ui-droppable" style="position: 
absolute; height: 70px; width: 70px; left: 264.433px; top: 111.1px;">
  <svg style="position:absolute;left:0px;top:0px" width="70" height="70" pointer-events="all" position="absolute" version="1.1" xmnls="http://www.w3.org/1999/xhtml">
    <circle cx="35" cy="35" r="35" version="1.1" xmnls="http://www.w3.org/1999/xhtml" style="stroke:url(#jsplumb_gradient_70)" fill="#3232c8" stroke="#666">
    <radialGradient id="jsplumb_gradient_70" version="1.1" xmnls="http://www.w3.org/1999/xhtml">
  </svg>
</div>

Original issue reported on code.google.com by j.verdur...@2bmore.nl on 26 Jan 2012 at 9:44

GoogleCodeExporter commented 8 years ago
this is fixed in 1.3.5.

Original comment by simon.po...@gmail.com on 27 Jan 2012 at 1:17

GoogleCodeExporter commented 8 years ago
1.3.5 was released today.

Original comment by simon.po...@gmail.com on 1 Feb 2012 at 1:57