IE6 Active Scripting Security Setting Behavior?

[Guest]

This question is directed to an internal Microsoft IE developer...

What is the difference between the way IE6 processes JavaScript with Active
Scripting Enabled verses Active Scripting is set to Prompt? We are
encountering an issue with an internal website on our intranet whose pages
will only load and display properly when Active Scripting is set to Prompt.
We started noticing this behavior when we installed the most recent security
patches to IE6. This behavior is consistent across PCs running WinXP Pro,
Wind2000 Pro, and even Win98SE!

A courtesy of a reply would be greatly appreciated. Thanks much!

 

[PA Bear]

Few if any "internal Microsoft IE developer" lurk in these peer-to-peer
newsgroups, David.

 

[Guest]

Oh well, just thought I'd pose the question here, thanks much for the reply!

This JavaScript IE6 behavior is quite perplexing. The only thing I can
assume at this point is that somehow this is a new undocumented security
feature of IE6. The JavaScript involved is rather simple. I'd be happy to
post it here if someone wants to take a look at it, thanks much.
- David

Few if any "internal Microsoft IE developer" lurk in these peer-to-peer
newsgroups, David.
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE/OE)

This question is directed to an internal Microsoft IE developer...

What is the difference between the way IE6 processes JavaScript with
Active
Scripting Enabled verses Active Scripting is set to Prompt? We are
encountering an issue with an internal website on our intranet whose pages
will only load and display properly when Active Scripting is set to
Prompt.
We started noticing this behavior when we installed the most recent
security
patches to IE6. This behavior is consistent across PCs running WinXP Pro,
Wind2000 Pro, and even Win98SE!

A courtesy of a reply would be greatly appreciated. Thanks much!