Details
Description
At the moment, the Reorderer provides a single callback: the orderChangedCallback. It is fired whenever the user has finished dropping an item.
However, there are a variety of interesting moments that should have callbacks:
* afterGrab(grabbedElement)
* afterMove(droppedElement)
* onSelect(selectedElement)
Other delegate-style predicate functions would be helpful to allow users to override the Reorderer's default behaviour?
* shouldSelect()
* shouldMove()
It would also be helpful if the orderChangedCallback was given a list of the new order of elements, saving users the effort of walking the DOM for simple cases.
dev-iteration43
However, there are a variety of interesting moments that should have callbacks:
* afterGrab(grabbedElement)
* afterMove(droppedElement)
* onSelect(selectedElement)
Other delegate-style predicate functions would be helpful to allow users to override the Reorderer's default behaviour?
* shouldSelect()
* shouldMove()
It would also be helpful if the orderChangedCallback was given a list of the new order of elements, saving users the effort of walking the DOM for simple cases.
dev-iteration43
Issue Links
| This issue relates to: | ||||
| FLUID-1048 | Simple Reorderer API function should include orderChangedCallback in options |
|
|
|