FLUID-479: Drop marker incorrect when avatar is dropped in white space at end of row.

Description

If browser window is resized so there is a lot of white space at the end of a row. Dragging and dropping an item in that white space will "snap" the dragged item back to its original position despite a drop marker being displayed at the end of the row.

Unrelated to Fluid-148.
Possibly related to Fluid-478.

Attachments

Comments

• Michelle D'Souza commented 2008-04-10T10:21:14.000-0400

  The underlying issue is that we don't hide the drop marker when we get an 'out' for the current drop target. This is because of the issue where we get 'over' and 'out' in the wrong order which causes great user confusion especially when we have nested drop targets.

• Anastasia Cheetham commented 2008-05-13T13:22:03.000-0400

  Possible solution: Modify the mouse move tracker to use the currentDroppable property if there is nod target. This will result in the item being dropped wherever the drop marker was last displayed.

• Antranig Basman commented 2008-08-08T08:53:23.000-0400

  This issue is very complex - the main constraints are
  i) We have a requirement to compute drop targets "manually" - since the default algorithm in JQuery UI cannot account for the "top half/bottom half" requirements when dragging things to between positions in lists,
  however
  ii) We are constrained also by the JQuery UI algorithm in that it will not give us drop notifications if the drop occurs outside any droppable target (in its opinion).

  However, the algorithm is valuable, in that it does some useful work for us quickly (determining which of the set of droppable targets we are "within tolerance" for a drop), which we must make use of via tracking of its over/out events which are sent.

• Antranig Basman commented 2008-08-08T10:27:27.000-0400

  Resolved as part of comprehensive drag and drop reorganisation at rev 5338 ("DragManager" created)

• Justin Obara commented 2008-11-13T13:29:45.000-0500

  appears to have been fixed