Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#2995 closed enhancement (fixed)

UI Sortables

Reported by: NeoAnderson Owned by: paul
Priority: major Milestone: 1.6b
Component: ui.sortable Version: 1.5
Keywords: UI Sortables Cc:
Blocked by: Blocking:


There is no provision of disabling the proxy used while dragging an element.

So, we can't move the original element without using proxy.

Change History (8)

comment:1 Changed 15 years ago by paul

Type: bugenhancement

That's true, but it's not a bug, but a enhancement request.

comment:2 in reply to:  1 Changed 15 years ago by NeoAnderson

Infact if a programmer writing code for dragging, then he assumes that user will be able to drag the original element, not the proxy. Instead, there should be an option to enable the proxy.

comment:3 Changed 15 years ago by NeoAnderson

Even after sorting, the iframe in original DIV is also getting refreshed. I think, this is a bug.

comment:4 Changed 15 years ago by rdworth


comment:5 Changed 15 years ago by paul

Resolution: fixed
Status: newclosed

this is fixed in the 1.6 branch - it supports the modes "original", "clone" and function and now defaults to "original".

comment:6 Changed 15 years ago by NeoAnderson

Which option needs to be used to change this?

comment:7 Changed 15 years ago by NeoAnderson

Even though I use original, when dragging is completed, the iFrame is getting refreshed.

How can I reopen it?

comment:8 Changed 15 years ago by tmoore


I'm dealing with the same problem myself. Unfortunately, there's nothing they can do about that. It's just the way browsers work: when you move an iframe (or the ancestor of an iframe) to a new position in the DOM, it reloads the iframe. The only way to prevent it is to avoid moving the iframe to a new DOM position and only move it using absolute positioning.

Note: See TracTickets for help on using tickets.