PDA

View Full Version : XP SP2 & IE 6 - Permission Denied scripting problem


Joe
September 17th 04, 05:28 PM
I develop a DHTML menu system that can function in a site with frames by
making cross-frame scripting calls.

I understand the security restriction of doing cross-frame scripting when
pages do not come from the same domain: You get a "Permission Denied"
javascript error.

However, only with IE 6 / XP SP2, I am getting a "Permission Denied" error
even when the frames contain pages that are from the same domain. The error
does not occur if the pages have the chance to completely load, it occurs
when the page in the target frame is in the process of loading. Prior to SP
2, this error did not occur (nor does it occur in any other browser /
windows combination I have tested).

Any information about this change that has occurred in SP 2, or tips to
resolve? The code itself is not doing anything inappropriate, and I have
very little to go on. I'm still trying things, but it has all been shots in
the dark.

Regards,

Joseph King
Coalesys, Inc

Robert Aldwinckle
September 19th 04, 01:02 AM
Check to see if your user has put About:Blank into the Restricted
security zone. Then see if you are using any open methods with
an unspecified location. ;)


---


"Joe" > wrote in message
...
>I develop a DHTML menu system that can function in a site with frames by
> making cross-frame scripting calls.
>
> I understand the security restriction of doing cross-frame scripting when
> pages do not come from the same domain: You get a "Permission Denied"
> javascript error.
>
> However, only with IE 6 / XP SP2, I am getting a "Permission Denied" error
> even when the frames contain pages that are from the same domain. The error
> does not occur if the pages have the chance to completely load, it occurs
> when the page in the target frame is in the process of loading. Prior to SP
> 2, this error did not occur (nor does it occur in any other browser /
> windows combination I have tested).
>
> Any information about this change that has occurred in SP 2, or tips to
> resolve? The code itself is not doing anything inappropriate, and I have
> very little to go on. I'm still trying things, but it has all been shots in
> the dark.
>
> Regards,
>
> Joseph King
> Coalesys, Inc
>
>

Google