Sortover/sortout changes from jquery 1.9 (and inconsistencies)

See:

http://jsfiddle.net/3X2bL/2/

Status 1 and status 2 record the last sortover or sortout event seen by the first and second lists respectively. If you drag an item from list 1 over list 2 you'll see Status 2 change to "sortover" if you drag the item BELOW list 2 (i.e. not back over list 1) you'll see Status 2 change to "sortout". If you then drag the item back into list 2 you'll not see Status 2 change. If you then drag the item back over list 1 you'll see Status 1 change to "sortover". If you then drag the item back over list 2 you'll see Status 1 change to "sortout" and Status 2 change to "sortover".

Perhaps related to this is in jquery UI 1.9 when you start dragging an item within a sortable list the "sortover" event is called and if you drag the item outside the list the "sortout" event is called. With 1.10 you don't get that initial "sortover" call and if you drag an item below the list it's in (i.e. outside of it, but not over a connected list) the "sortout" event doesn't fire at all. However if you drag that item over a connected list then back to its original list and drag it outside the original list then "sortout" does fire.

I haven't fully worked through the code, but from a quick skim I'm wondering if the first problem is down to the fact that when the list item is dragged outside the sortable "this.currentContainer" is still pointing to the last sortable the item was over.

The trigger for "over" is called after this piece of code:

if(this.currentContainer === this.containers[innermostIndex]) {
    return;
}

So because you've dragged the item back over the container already set in "this.currentContainer" then the "over" event isn't fired.

Now the trigger for "out" is called in this piece of code:

                                // container doesn't intersect. trigger "out" event if necessary
                                if(this.containers[i].containerCache.over) {
                                        this.containers[i]._trigger("out", event, this._uiHash(this));
                                        this.containers[i].containerCache.over = 0;
                                }

Now in the initial state of starting to drag an item from a sortable I don't think "containerCache.over" will have been set for that sortable because no initial over is firing, hence why no "out" gets called when dragging out initially.

This may well be related to #9335 (that talks about dragging draggables over sortables though). It may well also be related to what's described in #9099.