Javascript error occuring on new build machine

[Kevin S]

All,

I have already published this question in the
microsoft.public.internetexplorer.general group but figured it was
worthwhile to hedge my bets and put it in a javascript one as well.

My company is rolling out new windows laptops. One of the in-house
apps is generating a javascript error on the new laptops.

On the face of it the set up is the same (Windows XP, IE6 with SP2).

The error message is 'permission denied'.

Before I start debugging the application and changing code, can anyone
point me in the direction of what I should be checking, firstly for
possible differences in the set up and secondly of other issues I
should be considering with I perhaps am not aware of?

Thanks

 

[Thomas 'PointedEars' Lahn]

My company is rolling out new windows laptops. One of the in-house
apps is generating a javascript error on the new laptops.

On the face of it the set up is the same (Windows XP, IE6 with SP2).

And I thought they are selling new Windows laptops only with pre-installed
Vista and IE 7 by now.

The error message is 'permission denied'.

"Doctor, my arm hurts if I move it!"

Before I start debugging the application and changing code, can anyone
point me in the direction of what I should be checking, firstly for
possible differences in the set up and secondly of other issues I
should be considering with I perhaps am not aware of?

Different default security settings/precautions caused by different patch
levels, for example.

<http://catb.org/~esr/faqs/smart-questions.html>


PointedEars

 

[The Magpie]

I have already published this question in the
microsoft.public.internetexplorer.general group but figured it was
worthwhile to hedge my bets and put it in a javascript one as well.
[snip]

The error message is 'permission denied'.

That's like saying "I have a headache" and expecting the doctor to
realise you have a brain tumour. Needs a little more detail...

 

[Stevo]

The error message is 'permission denied'.

The most common reason I know of for seeing this message, is when
something in an iframe is trying to access it's parent page, or it's
parent page is trying to acccess something in the iframe. Standard
cross-domain scripting restriction. As to why the new machines are being
affected but presumably the old ones aren't, perhaps the older machines
had their browser settings tweaked to allow this to happen, and by
default the new ones aren't allowing it (which is the correct setting).

 

[Kevin S]

More detail? How's this?

The design off the application at this point of failure involves a web
page with a button which launches a modal dialog for the user to
select a value from. This value is then returned to the calling page.

The calling page where the value gets set is in a javascript file in
the directory
<<HomeDir>>\Jscript\Custom

using the code
oReturn = window.showModalDialog("dialogs/location/location.asp",
oArguments, "dialogHeight:480px; dialogWidth:640px;")
if (oReturn!=-1)

The error occurs on the if statement presumably because the value
comes from a window in a file in the directory
<<HomeDir>>\dialogs\location\

It would appear to be a Single Source Policy situation but why would
it work on one machine and not the other.

Also the root home directory is common to both so is there a way to
make the laptops recognise the fact that the directories are all from
the same source (i.e. root home directory)?