greedyChild of a parent droppable is not set to false after dropping on a greedy child. Also, the greedyChild is sometimes set to true, if a draggable intersects with a child droppable that does not accept the draggable. In that case the parent should receive the over event, but doesn't since greedyChild===true.

I believe this to be a bug, since the first time you drag something everything works as expected. However, after dropping on a child and adding a new droppable to the parent droppable can cause in the hoverClass to be applied incorrectly. Dropping seems to work as expected, but the end uses does not receive timely feedback from the hoverClass.

See the JSFiddle at http://jsfiddle.net/p4nm4/2/. The first time you drag "dragContainer", the hoverClass is applied to the container, regardless if you hover over a child. After dragging "dragChild" or "dragBoth" onto a child, then dragging "dragContainer" will not always be applied to the container when required.

My current workaround is to set the visible and greedyChild properties to false for all droppables inside $.ui.ddmanager.prepareOffsets. So placing the following at the beginning of the droppablesLoop.:

m[ i ].greedyChild = false;
m[ i ].visible = false;

Does anybody see a better way to work around this problem, because I do not like changing jQuery functions, since I may not be aware of a lot of things that are going on there. Or is this perhaps something that I can/should submit to the bug tracker in the hope that it will be fixed in an upcomming release?.