My html page is comprised of two frames both pint to secure URL's. When I attempt calling any functions on the document object via JS I get an Access is denied error in IE. How could I overcome this does anyone know? Is this happening becaus I am pointing to https URL's?
Thanks for the question. I meant to write up the same one, but haven't found the time. I had frame interactions working quite well before, including (before Ajax) doing ajax through iframes. (Capital A indicates official Ajax.) I'm now running IE 7 and things do not seem to be working as before; at least not my latest attempt to use an iframe for a cheap and dirty trick.
I'd post code, but I'd probably have to post a lot of it. I went through quite a bit of trial and error. Maybe you could post some code to get this started.
I'm currently experiencing a similar problem. In general, here's what I have:
1. A document with an anchor tag in it. This document contains a reference to an external js file. There are no js functions built into the document.
2. When the link is clicked, a js function is called to create a new window, keeping a handle to it in a global reference. The click action also fires off an Ajax request.
3. The function that receives the Ajax response adds a FORM to the document in the second window, targeting the response to itself (the second window). (Creating a new window in advance of the Ajax request/reponse is done to avoid a popup blocker.)
Both windows/pages are on the same domain. No JS functions exist in the window opened in step #2 above.
"uncaught exception: Permission denied to get property Window.timerId"
Firefox does not provide a statement # for the error, and I've been unable to catch it with a try/catch block.
My global variable for the second window is defined like this:
Smattered throughout a few different functions in the external js file are the following various references to the "ssoWindow" object:
One other clue: the only time the error shows up is when the process flows through using a GET -- which hints that it might be related to the following statement (but I don't think I could trap the error there):
If you know what might be causing this problem, please let me know. Thanks.