Allow portlets to be dragged into empty columns
Description
Environment
duplicates
relates to
Activity
Michelle D'Souza February 22, 2011 at 9:27 PM
Closing issues that were resolved for 1.0 and earlier releases.
Anastasia Cheetham March 27, 2008 at 3:38 PM
Regarding the above-mentioned issue "if a portlet is dragged quickly over another portlet, the drop marker is incorrectly displayed at the end of the column instead of relative to the target portlet":
With the 'greedy' flag on (which it is), the column should get an 'out' event when the dragging cursor moves from the column space into the portlet space, and on this out, we unbind the mousemove handler, trackMouseMovement() (which is what displays the dropMarker) from the column (and bind it to the portlet on the portlet's 'over').
We are getting the out event, and hence we are calling unbind(), but the mousemove handler continues fire, and hence continues to incorrectly display the dropMarker. So it looks like the unbind() is not properly unbinding.
Anastasia Cheetham March 26, 2008 at 7:46 PM
Navigating with the keyboard over an empty column is now implemented.
Michelle D'Souza March 26, 2008 at 6:26 PM
Using the keyboard to move into an empty column is now working.
Navigating with the keyboard over an empty column is not implemented yet.
Anastasia Cheetham March 25, 2008 at 8:27 PM
Also, currently you cannot use the keyboard to move portlets into an empty column.
This entails rethinking our definition of a drop target to allow empty columns to be drop targets, rather than only treating portlets as drop targets.