FLUID-1055: cannot move element to top of list (sortable vertical list)

Metadata

Source
FLUID-1055
Type
Bug
Priority
Critical
Status
Closed
Resolution
Cannot Reproduce
Assignee
Antranig Basman
Reporter
Herb Wideman
Created
2008-07-29T11:02:01.000-0400
Updated
2008-11-13T13:38:26.000-0500
Versions
  1. 0.4beta1
Fixed Versions
  1. 0.5beta1
Component
  1. Reorderer

Description

drag and drop of element to top of list does not work when it should - avatar when let go rebounds to original position.
This bug is not generated only by dragging the
list item way above the list and then attempting a drop; even if I
slowly move the item avatar upwards and drop as soon as the move
indicator bar appears in the top position in the list, the drop does not
work, it is simply impossible to move the item to the top position. So
it would appear this problem is not a duplicate of the "Drop target
appears when avatar not in a valid drop position" bug .

Environments

XP SP3, IE7

Comments

  • Herb Wideman commented 2008-07-31T16:12:21.000-0400

    he bug I am finding is not generated by dragging the
    list item way above the list and then attempting a drop; even if I
    slowly move the item avatar upwards and drop as soon as the move
    indicator bar appears in the top position in the list, the drop does not
    work, it is simply impossible to move the item to the top position. So
    it would appear this problem is not a duplicate of the "Drop target
    appears when avatar not in a valid drop position" bug

  • Antranig Basman commented 2008-08-08T11:15:31.000-0400

    There has been a considerable reorganisation of the drag and drop code at revision 5338 which has probably resolved this issue - certainly I am not able to reproduce it now.

  • Anastasia Cheetham commented 2008-08-08T11:30:52.000-0400

    I also cannot reproduce this one. I will let Justin confirm and close. Herb, if you can still reproduce it, it would be helpful if you could provide us with the page you are testing on, and more details about how you reproduce it.

  • Justin Obara commented 2008-11-13T13:38:26.000-0500

    Appears to have been fixed