ansaurus

Question

IE Operation Aborted - None of the regular fixes work!

Answer 1

+2 A:

There are several causes for this. Two of the most common are:

1) scripts attempting to modify the DOM before the document has completely loaded

2) Trailing commas in object or array declarations

Number two is usually relatively easy to find, while number one is much tougher. Generally the best way to track down IE Javascript problems is to install Microsoft Script Debugger, so at least you can see what lines are causing the problem. With Script Debugger, IE will halt execution inside the browser and kick the script to a Script Debugger console, which will show the problem line. Much more informative than regular IE error messages.

zombat 2009-05-06 21:48:28

As an aside, I ran into this with a Facebook application utilizing MooTools. It was usually a problem with code running inside the 'domready' event. 90% of the time the fix was to move the code to an 'onload' event, which fires much later after the entire document is ready to go, and not just the dom.

zombat 2009-05-06 21:50:48

Visual Studio (Web Developer Express is free if you don't have the full version) tends to work more reliably for me than the script debugger. A short HOWTO: http://www.berniecode.com/blog/2007/03/08/how-to-debug-javascript-with-visual-web-developer-express/

steamer25 2009-05-06 21:54:17

@steamer25 - ooh! shiny!

zombat 2009-05-06 21:58:48

Thanks zombat. I installed MS Script Debugger, and I haven't gotten the operation aborted error since. Unfortunately, the error just stopped happening. I tried disabling all third party add-ons (tools > internet options > advanced) and the problem was still gone. Now I have no idea what I did to fix it. I'm thinking it must have been some sort of cashing error where IE didn't actually refresh properly (even though view source was updated?) I'm stumped. Going to release it to my team of testers to see if they get the error. Thanks!

Peter Di Cecco 2009-05-07 13:23:00

Hmm, glad to hear it's not longer a problem. Hopefully it won't come back!

zombat 2009-05-07 17:03:57

Answer 2

A:

That problem can be a bear on a large page. Beyond the advice in the articles you already have, the only thing I can suggest from here is to remove wide swaths of the page in a dev environment until the problem goes away. Keep refining what is/is not on the page until you know which piece of content is causing the problem.

I've actually seen a confluence between two unrelated page elements cause this problem. I don't remember excisely why but the above approach, although painstaking, still worked.

steamer25 2009-05-06 21:50:10

My last resort... hope it doesn't come down to this...

Peter Di Cecco 2009-05-07 13:23:33

Answer 3

+1 A:

Please see my answer to this question in another thread. I love this little trick and it has never failed me (when the cause is DOM manipulation before IE is ready, I mean). And as written, it doesn't affect the DOM-compliant browsers.

pluckyglen 2009-05-07 00:38:06

ansaurus

tags:

views:

answers:

IE Operation Aborted - None of the regular fixes work!

related questions