Changing/setting connectWith option on start event not kicking in right away

[marventus.wp]

Hello. While working with 3 sortable lists, I came up with the following problem, but not 100% sure if it's a but or intended behavior.

In my example, items in lists 1 and 3 can be sorted inside their respective lists and connect with list 2 only. For example, list 1 connects with list 1 and list2 and not list 3.

When list1 and list3 items are dropped inside list2, I needed for that rule to still apply, so I tried to change list2's connectWith option on the sortstart event. However, the result is not the one I was expecting, since the item first needs to be dropped in the source list (i.e., list2) before the start function kicks in. This also seems to occur with the sort event as well.

Example of issue: ​http://jsfiddle.net/Marventus/Ud69M/

Expected behavior: ​http://jsfiddle.net/Marventus/Ud69M/1/

[Scott González]

This is not a bug. You can't wait until after the targets are determined to update the target.

[marventus.wp]

If you don't want to call it a "bug", call it a feature if you like. Not being able to bind list items to their original sortables would be a nice feature, since I don't see any other way of doing this with the current specs. I am of course open to the possibility I may be missing something.

[Scott González]

Duplicate of #7590.