Skip to main content

Bug Tracker

Side navigation

#14680 closed bug (cantfix)

Opened January 09, 2014 12:34PM UTC

Closed April 14, 2014 01:26PM UTC

Permission denied in IE11 when using top context jQuery from IFRAME

Reported by: Owned by:
Priority: undecided Milestone: None
Component: unfiled Version: 2.1.0-beta2
Keywords: Cc:
Blocked by: Blocking:

When a FORM in an IFRAME is submited BEFORE the document in the IFRAME is completly loaded and in the ONSUBMIT handler of the FORM is used jQuery from the top context (top.$(...)) then after the IFRAME is reloaded after postback, the jquery in the top context always throws the "Permission denied" error.

Simple example with described error (problem only in IE11) - the form in the IFRAME is submited automatically with script (for simulating the state when the document is not completly loaded):

When the form is submited after the document is completly loaded, everything works fine.

When using of top context jQuery is commented in the onsubmit handler, everything works fine.

jQuery version: 2.1.0-beta3

Probably the same problem as in the ticket #14535, but probably still not fixed in 2.1.0-beta3.

Attachments (0)
Change History (3)

Changed March 16, 2014 04:04PM UTC by dmethvin comment:1

owner: →
status: newpending

I'm inclined to say we can't fix this. In general, attempting to do cross-frame manipulation with jQuery is always a crapshoot. With IE, even more. Do you have any proposed solution @vkymla?

Changed March 24, 2014 10:19AM UTC by comment:2

status: pendingnew

Our workaround is to wait till the document in the iframe is completely loaded and only then use the "top context" jQuery.

We don't mind, that the jQuery is not working properly during the first request (during the iframe is not completely loaded), but the bad is, that from that moment is the "top context" jquery unusable (also for the code in the top context) and whole browser window must be reloaded...

Changed April 14, 2014 01:26PM UTC by dmethvin comment:3

resolution: → cantfix
status: newclosed

Our way to "fix" this internally has been to avoid touching deadly properties. If your code asks to touch them there isn't much we can do. We could try to ignore your requests but that would lead to even more confusing behavior.