Search and Top Navigation
#2262 closed bug (wontfix)
Opened January 31, 2008 07:10AM UTC
Closed March 31, 2008 02:57PM UTC
Last modified March 18, 2010 02:07PM UTC
iFrame problem while using UI Sortables makeSortable
Reported by: | BNArun | Owned by: | codesquare |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | ui.core | Version: | 1.2.2 |
Keywords: | ui sortable makeSortable | Cc: | |
Blocked by: | Blocking: |
Description
I'm using new ui.sortables makeSortable method. When I'm using an iFrame in this, this iFrame is getting refreshed when dragging is started. Fortunately it is not refreshing it's contents while dragging is completed.
Attachments (0)
Change History (4)
Changed February 07, 2008 06:20PM UTC by comment:1
owner: | paul → codesquare |
---|
Changed March 31, 2008 02:57PM UTC by comment:2
resolution: | → wontfix |
---|---|
status: | new → closed |
The problem is that the drag helper is a clone of the sortable which means it has to create a new iframe (as well as all the other dom nodes) to build the sortable/draggable helper. You'll need to explore using a different helper method or building your sortables without iframes. If the iframe content is domain local you could use an ajax call to get the iframe content and inject it as static content.
Changed May 24, 2008 03:39AM UTC by comment:3
milestone: | 1.2.3 |
---|
Milestone 1.2.3 deleted
Changed March 18, 2010 02:07PM UTC by comment:4
Replying to [comment:3 None]:
Milestone 1.2.3 deleted
FYI - the problem is more likley to do with this issue logged against ,mozillas firefox
https://bugzilla.mozilla.org/show_bug.cgi?id=254144
When an iframe is removed from the DOM, its content is reloaded.
I figure the safest solution is to not change the parent i.e. not remove the element from the DOM at all although i can see this causing further css related issues re zindexing and overlfow
This is something Firefox related. I don't know why it's happening though..