javascript erros when dragging to the same element as source

jnobre / jsplumb

Automatically exported from code.google.com/p/jsplumb

0 stars 0 forks source link

javascript erros when dragging to the same element as source #289

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

I can actually reproduce it on the flowchart demo 
(http://jsplumb.org/jquery/flowchartConnectorsDemo.html)

Steps:

- Square 4, drag Right Center target endpoint to it source (at Top Middle )

After that, all hell breaks loose: lots of js errors and this node is lost.

cheers,
Pedro

Original issue reported on code.google.com by pedr...@gmail.com on 30 Oct 2012 at 5:26

Attachments:

[Screenshot at 2012-10-30 15:17:47.png](https://storage.googleapis.com/google-code-attachments/jsplumb/issue-289/comment-0/Screenshot at 2012-10-30 15:17:47.png)

GoogleCodeExporter commented 8 years ago

this actually applies to any case where you drag a green endpoint on top of a 
blue one.  the errors reported can vary but all are caused by the same bug.

fixed in 1.4.0 dev.

Original comment by simon.po...@gmail.com on 4 Nov 2012 at 1:39

Added labels: 1.4.0

GoogleCodeExporter commented 8 years ago

Original comment by simon.po...@gmail.com on 7 Nov 2012 at 7:32

Changed state: Fixed

GoogleCodeExporter commented 8 years ago

When's 1.4.0 being released?

Original comment by t...@xemware.com on 8 Jan 2013 at 9:01

GoogleCodeExporter commented 8 years ago

i don't know. soon, i hope.

Original comment by simon.po...@gmail.com on 8 Jan 2013 at 9:06

GoogleCodeExporter commented 8 years ago

Issue 313 has been merged into this issue.

Original comment by simon.po...@gmail.com on 25 Jan 2013 at 2:10

GoogleCodeExporter commented 8 years ago

Hello! I just tested from the master at github and the problem still happens 
with 1.4.0-RC1.

It happens when dragging the connection from its source endpoint to the 
"target" element (that contains the source endpoint)

I tried to intercept on beforeDrop, but not sure how to detect and avoid the 
bug. Any workaround? 

I also noted that some connections are different (maybe not applying css) on 
the version form the master, not sure if you are aware.

cheers.

Original comment by pedr...@gmail.com on 30 Jan 2013 at 12:51

Attachments:

[Screenshot from 2013-01-30 10:50:03.png](https://storage.googleapis.com/google-code-attachments/jsplumb/issue-289/comment-6/Screenshot from 2013-01-30 10:50:03.png)
[Screenshot from 2013-01-30 10:49:44.png](https://storage.googleapis.com/google-code-attachments/jsplumb/issue-289/comment-6/Screenshot from 2013-01-30 10:49:44.png)

GoogleCodeExporter commented 8 years ago

not sure if it's clear the sequence to reproduce, skipped a attachment in the 
previous comment. Attaching it here.

Original comment by pedr...@gmail.com on 30 Jan 2013 at 12:56

Attachments:

[Screenshot from 2013-01-30 10:54:21.png](https://storage.googleapis.com/google-code-attachments/jsplumb/issue-289/comment-7/Screenshot from 2013-01-30 10:54:21.png)

GoogleCodeExporter commented 8 years ago

you'd need to provide jsfiddle with your code in.  on the jsplumb demo in 1.4.0 
it works.

Original comment by simon.po...@gmail.com on 31 Jan 2013 at 12:01