We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dragging a item accross rows adds follow code between the rows:
<li class="item ui-sortable-placeholder" style="visibility: hidden; "></li>
But it doesn't move them after a drop and the list is not draggable after that anymore at all.
This seems to occur when you cross to a sublist.
Please see the short attached video showing this issue:
http://screencast-o-matic.com/watch/cl6ZbjSuO
The text was updated successfully, but these errors were encountered:
Hi, it has never occured before, it must have something to do with your specific configuration, or some conflicting javascript.
2012/10/24 Saman notifications@github.com
Dragging a item accross rows add follow code between the rows: But it doesn't move them after a drop and the list is not draggable after that anymore at all. This seems to occur when you cross to a sublist. Please see the short attached video showing this issue: http://screencast-o-matic.com/watch/cl6ZbjSuO — Reply to this email directly or view it on GitHubhttps://github.com//issues/59.
Dragging a item accross rows add follow code between the rows:
— Reply to this email directly or view it on GitHubhttps://github.com//issues/59.
Sorry, something went wrong.
Issue solved, was my fault, due to faulty html.
No branches or pull requests
Dragging a item accross rows adds follow code between the rows:
But it doesn't move them after a drop and the list is not draggable after that anymore at all.
This seems to occur when you cross to a sublist.
Please see the short attached video showing this issue:
http://screencast-o-matic.com/watch/cl6ZbjSuO
The text was updated successfully, but these errors were encountered: