"permission denied" reading window props

[Composer]

Newbie alert here....

I'm about half way through the "JS Definitive Guide" and it's been going fine, until.... I got to all the code examples about creating new windows and then moving them, setting and reading properties. Whenever I try to run this in IE6 I get an "access is denied" error. So where the heck's the little checkbox I have to toggle on or off somewhere??

Thanks.

[TrueLies]

I stumbled into your very same problems with .... Netscape 7 (yeah, seven! the pre release: we have NN4.79, arguably leading to NN5, then NN6, NN6.2.3 and NN 7.0 No, comments not necessary LOL): it breaks up when attempting to read window.fullScreen: recognizes such object but denies the authorization: I had to work around it and bypass. Some properties seem just can't be inspected via scripting.

You can have fun with my browser stripper to see what properties can be checked:

http://www.unitedscripters.com/hotvamps/browsers.html

Anyway if it is a pop up odds are that the code is wrong. Please post it, I hope tomorrow I remember to check or someone else may.

ciao

[Composer]

the "bad" code

Well, I suppose it could be wrong. Here's the entire thing:

<SCRIPT>
var myWin = window.open("http://microsoft.com");
var myLoc = myWin.location.toString();
prompt (myLoc);
</script>

The new browser window opens as expected, but then I get:
Runtime Error: Line 2 - Permission is denied.

This is in IE 6.

Help!

Jeffery

[joh6nn]

try this:

<SCRIPT>
var myWin = window.open("http://microsoft.com");
var myLoc = myWin.location.href;

</script>

[Composer]

Thanks John.

Your script:

<SCRIPT>
var myWin = window.open("http://microsoft.com");
var myLoc = myWin.location.href;

alert(myLoc);

</script>

Still gives me "permission denied".

I am realizing now that I get two distinct messages, although I don't know what's different -- sometimes I get "permission denied" and others "access denied".

I also tried Netscape 6.2 -- no error is reported but the alert displays "about: blank".

[joh6nn]

sorry, dude, i wasn't paying enough attention before. i just noticed, you're opening microsoft.com in the other window. javascript has what's called the "same source" policy, where scripts can only work with pages that come from the same domain as themselves. you're never going to get a handle on that window, because with microsoft's page in it, it doesn't belong to you anymore. you'd have to have your own page in their to work with it.

[Composer]

Ah ha!

Thanks, John. That was it... he in fact explains that pretty clearly in the book, but it was one of those tidbits of information that I glossed over...