Flame Damnation

General Category => General Forum => Topic started by: caskurô on May 25, 2009, 02:22:32 am



Title: Operation Aborted
Post by: caskurô on May 25, 2009, 02:22:32 am
http://support.microsoft.com/kb/927917

This problem occurs because 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.

For example, this problem may occur 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.

For more information about this error, visit the following Microsoft Web site:
What Happened to Operation Aborted?
http://blogs.msdn.com/ie/archive/2008/04/23/what-happened-to-operation-aborted.aspx (http://blogs.msdn.com/ie/archive/2008/04/23/what-happened-to-operation-aborted.aspx)
Note Users may also receive this error message if a Web page in a Trusted Sites Zone sends a HTTP 302 redirect to a page in the Internet Zone. With protected mode, Internet Explorer 7 and later versions that are running on Windows Vista or a later operating system prevent redirects from Web pages that run at medium integrity to Web pages that run at low integrity for security reasons. In these scenarios, users may receive a similar "Operation Aborted" error message. To resolve this issue, make sure that HTTP 302 redirects are for pages within the same zone. For example, make sure that a redirect is from one Trusted Sites Zone page to another Trusted Sites Zone page. Or, make sure that both the source and the destination of the redirect don't involve a change in Internet Explorer's protected mode status.
Back to the top
Workaround 1
To work around this problem, write script blocks that modify only closed containers or that modify only the script's immediate container element. To do this, you can use a placeholder to close the target container, or you can move the script block into the container that you want to modify.
Back to the top
Workaround 2
You can turn off friendly HTTP error messages in Internet Explorer. This workaround still lets the error message appear. However, Internet Explorer does not move away from the page after the error occurs. This workaround works only for Internet Explorer 6.

To do this, follow these steps:

   1. On the Tools menu, click Internet Options.
   2. On the Advanced tab, click to clear the Show friendly HTTP error messages check box under the Browsing section, and then click OK.
   3. Close the browser.

Back to the top
Workaround 3
You can 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.

For Internet Explorer 7, use one of the following methods.
Method 1
Add the individual site to Restricted Sites where scripting is disabled by default.

Note This method affects not only scripting but also many other areas of the page, including ActiveX controls, that are disabled or set to prompt for this zone.

To do this, follow these steps:

   1. On the Tools menu, click Internet Options.
   2. On the Security tab, select the Restricted Sites zone.
   3. Click Sites, click Add, and then click OK.

Method 2
Set the Active Scripting to Prompt or to Disabled when you view an affected site for the zone in which the site loads.

Note This setting affects all the sites in the zone and should be set back to Enabled when you browse other sites. Determine what zone the site is loaded under by viewing the lower-right corner of the Status Bar.

   1. On the Tools menu, click Internet Options.
   2. On the Security tab, select the zone the site loads under.
   3. Scroll down to the Scripting section, and set the Active Scripting to Disabled - prevents scripts or to Prompt - prompts user to run or not to run scripts.
   4. Click OK.

Note Method 1 and method 2 for Internet Explorer 7 may make the site unusable. Only disable scripts if the issue occurs frequently on the same site. If you change the Scripting setting, make sure that you reset the setting back to Enabled afterward so that other sites in that zone are not affected. If you cannot disable scripting, use Workaround 1, or upgrade to Internet Explorer 8.