Search and Top Navigation
#2995 closed enhancement (fixed)
Opened June 12, 2008 12:45PM UTC
Closed July 03, 2008 10:55PM UTC
Last modified August 27, 2008 06:41AM UTC
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: |
Description
There is no provision of disabling the proxy used while dragging an element.
So, we can't move the original element without using proxy.
Attachments (0)
Change History (8)
Changed June 16, 2008 07:42PM UTC by comment:1
type: | bug → enhancement |
---|
Changed June 17, 2008 11:14PM UTC by comment:2
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.
Changed June 24, 2008 07:28PM UTC by comment:3
Even after sorting, the iframe in original DIV is also getting refreshed. I think, this is a bug.
Changed June 26, 2008 07:50PM UTC by comment:4
milestone: | 1.5 → 1.5.2 |
---|
Changed July 03, 2008 10:55PM UTC by comment:5
milestone: | 1.5.2 → 1.6b |
---|---|
resolution: | → fixed |
status: | new → closed |
this is fixed in the 1.6 branch - it supports the modes "original", "clone" and function and now defaults to "original".
Changed July 22, 2008 02:46PM UTC by comment:6
Which option needs to be used to change this?
Changed August 23, 2008 06:40PM UTC by comment:7
Even though I use original, when dragging is completed, the iFrame is getting refreshed.
How can I reopen it?
Changed August 27, 2008 06:41AM UTC by comment:8
NeoAnderson,
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.
That's true, but it's not a bug, but a enhancement request.