Mitch,
I've tracked down the culprit. I'm using location.search to alter the
query string in the URL. After calling this, as a side effect,
subsequent calls trying to access frames fails with the access
violation. Any ideas?
-todd
Mitchell Stoltz <[EMAIL PROTECTED]> wrote in message
news:<[EMAIL PROTECTED]>...
> You shouldn't be seeing acces denied errors if both pages and the
> frameset are all on the same server. If the frameset is on a different
> server, you will get errors, but I'm planning to change this (see bug
> 52920). If everything's on the same server and you're still being
> denied, this is another bug but I can't diagnose it without a minimal
> testcase.
> -Mitch
>
> Heikki Toivonen wrote:
>
> > A minimal testcase would help in analyzing the problem. In any case,
> > n.p.m.security is probably a better place to discuss this, Cc &
> > Followup-To set.
> >
> > Todd Berry wrote:
> >
> >> Accessing a form in a frame(which worked fine in NS 4.x) gives me the
> >> error access denied. The javascript is the following
> >> parent.parent.frames["left"].frames["tree"].document.forms[0]
> >>
> >> It doesn't matter how I reference the frame "tree"- I can use top.
> >> instead of parent.- same error. This doesn't occurr in every instance,
> >> so I'd like to know why I get this at all. All of the frames are on my
> >> domain, so I'm not references a different url(which is one reason it
> >> appears you can receive this error.)
> >>
> >> The error under 6.01 is NS_ERROR_DOM_PROP_ACCESS_DENIED (1010). In NS
> >> 6.1 it's simply "uncaught exception: Permission denied to access
> >> property".
> >>
> >> This is occurring on Win2000 with NS 6.01 and NS 6.1.
> >>
> >> PLEAE HELP before we chunk NS 6 support.
> >>
> >> Thanks
> >>
> >
> >
