FYI, Droppables don't play nicely with fixed positioning. Scroll offset is added to the position of the Droppable, which is wrong in the case of its position being fixed. This throws off the hover calculation. Seems like the "right" way to check for hover that would deal with this without breaking normal usage is to check the location of the Draggable and the Droppable relative to the viewport, but I assume that's too expensive to calculate on mouse drag. Alternatively, just walking the parent tree checking for position: fixed would do it too (when creating the Droppable would probably due, though on-drag-start would be more reliable).
In my case, all of my Droppables are fixed, so I just hacked up the hover formula to remove the scroll offset. Also, since I'm here, might as well point out: I've noticed that there's a little glitch when using cursorAt and revert. It reverts the cursorAt position back to the initially clicked position. So if I have cursorAt set to the center of the object, and I start the click-and-drag near a corner, the center of the object will revert back to that corner. But generally, interface is amazing! Awesome work! --Erik
_______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
