Skip to main content

Search and Top Navigation

#9067 closed bug (duplicate)

Opened February 07, 2013 02:48PM UTC

Closed September 30, 2013 09:29AM UTC

New stacking feature causing iframe problems when changing active dialog

Reported by: aNt1X Owned by: aNt1X
Priority: minor Milestone: none
Component: ui.dialog Version: 1.10.0
Keywords: Cc:
Blocked by: Blocking:


Talking about the following commit:

The new moveToTop() function breaks iframe usage because of this line of code:

var moved = this.uiDialog.nextAll( ":visible" ).insertBefore( this.uiDialog );

The insertBefore() usage makes the iframe to be detached and reattached from the DOM; you can have occasional javascript errors or entire iframe refresh, depending on which browser you use; i think it is because of this:

What do u think?

I know it's not a jQuery ui problem, but how can we avoid this ?

Thank you for your work.

Attachments (0)
Change History (7)

Changed February 07, 2013 02:49PM UTC by aNt1X comment:1

Sorry guys, i left the component setting of this ticket to "ui.core" but it is "ui.dialog".

Sorry again.

Changed February 07, 2013 02:53PM UTC by scottgonzalez comment:2

component: ui.coreui.dialog
owner: → aNt1X
status: newpending

I think browser vendors should fix this. Do you have any suggestions?

Changed February 07, 2013 03:36PM UTC by aNt1X comment:3

status: pendingnew

Not yet. I will further investigate it.

Vendors implemented this protection to avoid memory leaks (

We could modify the z-index only for those dialogs that contains an iframe, leaving the new mechanism for dialogs without an iframe, but it would be an ugly workaround, and the old z-indexes method caused many problems ...

Changed February 11, 2013 06:43AM UTC by mandana comment:4

I have the same problem after upgrading JqueryUI to 1.10

As there is no other way to move an ifram in DOM without loosing it's content, using z-index seems to be the only possible solution to this issue.

BTW I don't think of it as a minor bug!!!

Changed February 22, 2013 08:20PM UTC by mikesherov comment:5

resolution: → cantfix
status: newclosed

Nothing we can do here... Although, fortunately, now jQuery has a meta ticket in webkit for issues we need fixed. This has been added.

Commented here: and noted as a blocker here:

Changed September 30, 2013 09:29AM UTC by jzaefferer comment:6

resolution: cantfix
status: closedreopened

This is a duplicate of #9166 (or the other way round), which we're addressing on our end, since browsers declared WONTFIX. So the cantfix solution isn't correct anymore.

Changed September 30, 2013 09:29AM UTC by jzaefferer comment:7

resolution: → duplicate
status: reopenedclosed

Duplicate of #9166.