Rather than hide it you could remove it completely from the DOM.  If your
element isn't recreated via ajax after a drop, move it yourself after a
successful drop by removing it from the DOM and reinserting it where it was
dropped (or wherever makes sense for that matter if the target is sorted

On Mon, Sep 14, 2009 at 8:51 AM, ColinFine <colin.f...@pace.com> wrote:

> On Sep 11, 2:19 am, "Jon B." <jbernha...@gmail.com> wrote:
> > I'm trying to use the reverteffect option on a sortable and it's not
> > doing what I would expect. My expectation is that the reverteffect
> > would only be triggered if the object I'm dragging is dropped back
> > where it started. What I'm seeing is that the reverteffect is
> > triggered regardless of where I drop the object. I'm including a
> > simple example below.
> >
> I havent' used reverteffect or sortable, but I've used revert on
> draggable, with a similar result.
> It appears that it reverts irrespective of whether the drop succeeded
> or not.
> What I have done is to hide the dragged element when the drag
> succeeds, so that the revert is not visible. In my case, the dropsite
> is then regenerated in Ajax, so there is a brief moment when the
> element has disappeared, and then it appears again in its new home. I
> don't know if your instance could work that way.
> >

You received this message because you are subscribed to the Google Groups 
"Prototype & script.aculo.us" group.
To post to this group, send email to prototype-scriptaculous@googlegroups.com
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to