#3666 closed bug (fixed)
connectToSortable breaks if argument is array
Reported by: | Marc Diethelm | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 1.7 |
Component: | ui.draggable | Version: | 1.6rc2 |
Keywords: | draggable, sortable, connectToSortable, array | Cc: | |
Blocked by: | Blocking: |
Description
A draggable can be linked to a sortable in two ways: by setting 'connectToSortable' to a selector or to an array of selectors. Using an array fails to provide the expected functionality however, the sortable does not 'accept' the dragged item.
Attachments (3)
Change History (10)
comment:1 Changed 14 years ago by
Milestone: | TBD → 1.next |
---|
comment:2 Changed 14 years ago by
comment:3 Changed 14 years ago by
I'm attaching a patch that fixes this issue, and by testing it i realized another bug: #3787
comment:6 Changed 14 years ago by
Feb 12th:
Array works again, String fails. This is better. However the documentation states:
"Specifying this option as an array of selectors is deprecated." This needs to be changed.
comment:7 Changed 14 years ago by
Milestone: | 1.next → 1.6 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Support for arrays has been removed. You must specify a selector now. I've updated the docs. Thanks.
Note: See
TracTickets for help on using
tickets.
In 1.6rc4 the behavior is reversed. Now a single selector string produces no result while an array of selectors works. Filing a new bug #3739.