Why does ASP.NET cause the “Operation Aborted” Error in IE7?

Question

I have been reading lots of blog posts offering cause and solution to the \"Operation Aborted\" error in IE. I recently built an application that is getting this error for s

Answer 1

I understand why the error could occur. However, I don't see myself doing anything like that. My repeater doesn't have viewstate enabled and I am just doing a fresh rebinding using the collection.

How does a repeater databind correspond with appending something dynamically?

Answer 2

The intricacies of your collection and bindings have introduced a race condition.

The Operation Aborted error is an obscure IE bug, which occurs when the DOM is appended before the page is finished loading.

The Operation Aborted Error

Refer to this question: What is the Operation Aborted error in Internet Explorer?

This isn't intrinsically an asp.net problem, but, in your case, asp.net is failing to control the order of execution, due to the way you've written the databind. In other words, depending on the order in which resources load and execute (which current is not being controlled), the condition exists.

Incidentally, it may be harder to reproduce the condition in your development environment if you have some of these resources cached on the front end, or if they load more quickly (being available on a local network), which would explain why you're having trouble seeing the error.

Answer 3

See bug report here:

http://webbugtrack.blogspot.com/2008/08/bug-404-operation-aborted-in-ie.html

in short:

1. The HTML file is being parsed

2. script is executing

3. The executing script attempts to (add or remove) an element from an unclosed ancestor in the markup tree (excluding immediate parent of the script element)

The good news is that this is partially fixed in IE8.