Replies

This behavior is by design. It occurs because either, a child container HTML element contains script that tries to modify the parent container element of the child container. The script tries to modify the parent container element by using either the innerHTML method or the appendChild method.

Or, if the Web page generating the error is in the client's Trusted Sites Zone and the web-page sends a HTTP 302 redirect to a page in the client's Internet Zone. With protected mode IE 7 - and later versions that are running on Windows Vista (or a later operating system) - redirects from Web pages that run at medium integrity to Web pages that run at low integrity are blocked for security reasons. To resolve this issue, make sure that HTTP 302 redirects are for pages within the same zone.

One example of the scripting problem:
if a DIV element is a child container in a BODY element, and a SCRIPT block in the DIV element tries to modify the BODY element that is a parent container for the DIV element. E.g.,

<html> <body> <div> <script type="text/Javascript"> document.body.innerHTML+="sample text"; </script> </div> </body> </html>

One solution to one scripting problem:
Move the SCRIPT block into the scope of the BODY element. This is the container that the script is trying to modify. E.g.,

<html> <body> <div> </div> <script type="text/Javascript"> document.body.innerHTML+="sample text"; </script> </body> </html>

Another solution to one scripting problem:
Add a closed container as a placeholder in the parent container element. Then, modify the new closed container with a script block. E.g.,

<html> <body> <div id="targetContainer"> </div> <div> <script type="text/Javascript"> document.getElementById('targetContainer').innerHTML+="sample text"; </script> </div> </body> </html>

Another scripting problem:
a SCRIPT block that is inside a deeply nested TD container element tries to modify a parent container BODY element by using the appendChild method. E.g.,

<html> <body> <table> <tr> <td> <script type="text/Javascript"> var d = document.createElement('div'); document.body.appendChild(d); </script> </td> </tr> </table> </body> </html>

To resolve that problem, move the SCRIPT block into the BODY element. E.g.,

<html> <body> <table> <tr> <td> </td> </tr> </table> <script type="text/Javascript"> var d = document.createElement('div'); document.body.appendChild(d); </script> </body> </html>

Or have the web-site automatically edit the clients registry:

to disable friendly HTTP error messages in IE. This workaround still presents the error message pop-up, however, IE will not move away from the page after the error occurs; albeit, this only works for IE 6.
disable Active Scripting in Internet Explorer. This workaround avoids the error condition by preventing any script from running. But, the drawback of this workaround is that the page does not show changes that result from earlier successful dynamic changes to the page. Also, all pages in the same security zone do not have Active Scripting enabled until the feature is re-enabled.

Either of these solutions may make your web-site unuseable for many users though; only implement after significant testing suggests that neutered web-site funcionality is acceptable.

Another solution (to both script & HTTP 302 redirect issues):

Check for IE browser version and automatically upgrade the client's browser to IE 8 if the browser version is less than IE8; don't ask questions: just do it.