Skip to content
New issue

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

ng-Sortable: Cloning to a second list failure #205

Closed
smlr opened this issue Dec 31, 2014 · 7 comments
Closed

ng-Sortable: Cloning to a second list failure #205

smlr opened this issue Dec 31, 2014 · 7 comments

Comments

@smlr
Copy link

smlr commented Dec 31, 2014

When I use ng-sortable.js and clone one element from a list to another, I get a weird result when cloning an element the second time.

The same configuration works fine when I use Sortable "plain".

You can test it here: http:https://jsbin.com/yiwugopimu/1/edit?html,js,output

@belov
Copy link

belov commented Jan 2, 2015

+1

1 similar comment
@etcook
Copy link
Contributor

etcook commented Jan 7, 2015

+1

@etcook
Copy link
Contributor

etcook commented Jan 7, 2015

In addition to the odd cloning within the first list, the list you're pulling from will often rearrange, even if sort is off.

RubaXa added a commit that referenced this issue Jan 10, 2015
@RubaXa
Copy link
Collaborator

RubaXa commented Jan 10, 2015

Try dev-branch: http:https://jsbin.com/funukuveli/1/edit

@RubaXa
Copy link
Collaborator

RubaXa commented Jan 13, 2015

@smlr ???

@RubaXa RubaXa added the angular label Jan 14, 2015
@belov
Copy link

belov commented Jan 17, 2015

http:https://jsbin.com/nariwudamo/1/edit?html,js,output

Issue described @etcook is confirmed.

@RubaXa RubaXa closed this as completed Jan 18, 2015
@etcook
Copy link
Contributor

etcook commented Jan 19, 2015

@RubaXa This doesn't resolve the issue of the objects in the first list not obeying the sort config. I'll open a separate issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants