Hi, I played around with the subversion mochikit drag and drop support. One thing I noticed is that when a snapping-method is in place (regardless of its kind), things can get somewhat tricky regarding the isAffected-check that makes droppables target of the action in question.
The reason is simple: the isAffected call is evaluated using the current pointer position. However, snapping might introduce a significant bias between the placement of the draggable and the pointer. The remedy is simple: in case of options.snap not being false, use the current droppable element position instead. For the simple non-scrolling case, I have a patch available that demonstrates the doability - however, it is pretty "rough". I'd be happy working on it, as well as fixing the scrollable case, but due to my very dim understanding of CSS so far (I'm a noob on that), I can't imagine a way to create a test case. Any comments? Diez --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~----------~----~----~----~------~----~------~--~---
