You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
first of all, thank you very much for your fantastic FancyTree!
In my project, I am using Fancytree 2.26.0 and its drag&drop functionalities (dnd5) for building a tree from a grid containing the nodes to add; these items have "draggable" attribute.
All works wery well, and I am able to build trees from these data.
Unfortunately, I noted a bug that, for the final user, can be very disappointing.
If you perform a drag&drop of a node within the tree (i.e. if you move a node already in the tree in another position of the same tree), then the node (and sometimes also its direct father) becomes a "non-node" (from dnd5 point of view) and the user cannot drop "draggable" objects on it.
It seems that the "moveTo" function leaved the nodes in an inconsistent state.
But if you then perform a "false dnd" in the tree (i.e. drag a node, then drop it in a "not droppable" area, so the tree remains unchanged), the node (but I suspect, the entire tree) resets its status and the user can again drop a "draggable" on the same node that before refused it.
Of course, also saving the tree with the just moved node, then closing/reopening the page, allowed the user to drop "draggable" also over the same node that before refused it.
Of course, both these workarounds are not willing to be used in production environment.
In the "github_dnd5_bug_sample.html" attached file you can find a situation compatible with our production site (drag from a DataTables grid to a Fancytree).
Steps to reproduce the problem:
Create folder "example" at the same level of "lib" and "src" folders of Fancytree distribution
Copy github_dnd5_bug_sample.html into "example" folder
open github_dnd5_bug_sample.html page in your browser (Chrome or Firefox)
Drag some items from column "Name" of the table into the tree (i.e. as childs of "Drop here" node)
Drag a tree node (let's name it "moved001") as child of another node
Drag an item from column "Name" into the tree as child of "moved001" ---> the "forbidden" icon appear
Hello,
first of all, thank you very much for your fantastic FancyTree!
In my project, I am using Fancytree 2.26.0 and its drag&drop functionalities (dnd5) for building a tree from a grid containing the nodes to add; these items have "draggable" attribute.
All works wery well, and I am able to build trees from these data.
Unfortunately, I noted a bug that, for the final user, can be very disappointing.
If you perform a drag&drop of a node within the tree (i.e. if you move a node already in the tree in another position of the same tree), then the node (and sometimes also its direct father) becomes a "non-node" (from dnd5 point of view) and the user cannot drop "draggable" objects on it.
It seems that the "moveTo" function leaved the nodes in an inconsistent state.
But if you then perform a "false dnd" in the tree (i.e. drag a node, then drop it in a "not droppable" area, so the tree remains unchanged), the node (but I suspect, the entire tree) resets its status and the user can again drop a "draggable" on the same node that before refused it.
Of course, also saving the tree with the just moved node, then closing/reopening the page, allowed the user to drop "draggable" also over the same node that before refused it.
Of course, both these workarounds are not willing to be used in production environment.
In the "github_dnd5_bug_sample.html" attached file you can find a situation compatible with our production site (drag from a DataTables grid to a Fancytree).
Steps to reproduce the problem:
You can verify this behavior also in the dnd5 demo page (http://wwwendt.de/tech/fancytree/demo/#sample-ext-dnd5.html).
Steps to reproduce the problem (dnd5 demo page):
Did someone can help me to find a (programmatical) fix to avoid to the final user the empirical workarounds I described above?
Thank you very much!
Best Regards
ZioZione
github_dnd5_bug_sample.zip
The text was updated successfully, but these errors were encountered: