Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Invalid
-
Affects Version/s: 2.1-Beta2
-
Fix Version/s: 3.0
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ICEfaces 3, showcase
-
Assignee Priority:P3
-
Affects:Documentation (User Guide, Ref. Guide, etc.)
Description
When using the ICEfaces Showcase demo for ace:draggable "Draggable" (http://localhost:8080/showcase/showcase.jsf?grp=aceMenu&exp=draggableOverviewBean), if you enable the cloneHelper mode ("yes"), the draggable will no longer drop correctly.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
This is the defined behaviour of the clone handler. This should be documented better however.
Show
Nils Lundquist
added a comment - This is the defined behaviour of the clone handler. This should be documented better however.
To demonstrate this being the defined behaviour, open the following page:
http://jqueryui.com/demos/droppable/
Open the javascript console and enter:
$( "#draggable" ).draggable('destroy');
$( "#draggable" ).draggable(
);
And then drag the now helper:clone draggable into the droppable.
Show
Nils Lundquist
added a comment - - edited To demonstrate this being the defined behaviour, open the following page:
http://jqueryui.com/demos/droppable/
Open the javascript console and enter:
$( "#draggable" ).draggable('destroy');
$( "#draggable" ).draggable(
{helper:'clone'}
);
And then drag the now helper:clone draggable into the droppable.
This behaviour is because there is no drop zone in the example. When the clone handler is used, a transient copy of the original element is used during the drag.
The behaviour can be recreated using the pure jQuery code, or seen on the PF version of draggable:
http://www.primefaces.org/showcase/ui/draggableBasic.jsf
However, when I change the draggable overview example to use clone, which includes drop zones, it triggers the drop request as I'd expect but there is no change to the rendered view. I'm investigating why this is, a component or app deficiency.