OK… I’ve had a strange bug pop on occasionally for the last couple weeks, in which people surfing the site in Internet Explorer get the error “Operation Aborted” when surfing the main page. You don’t get it just reading any of the articles.
So does anyone out there have a clue? Firefox doesn’t see anything, and when that pop up comes up, it just stops loading and I can’t even see where on the site the error is, or have a look anywhere on what may be causing it.
Edits -
(4:24pm): Its not a <script> in a <table> bug. Or <div> in <table>. I opened in Firefox and have been doing searches in the code. Resource that had mentioned one fix.
(4:45pm)I don’t think I use mootools, but I’ll be checking the one popup I do have hand coded in.
(5:12pm) Slightbox uses MooTools. I disabled it, and it now the site works in ie7. But that sucks since I used it a lot in this blog. I’ll try and find a fixed version, or a equivalent to use instead.
(6:10pm) I found a version of Slightbox that was supposedly working April 15th… But not official download. I’m currently looking for an official one, but I reactivated it for the time being. Let me know if it still errors out for you. (worked for me).
Tags: Interesting, Internet Explorer, Irony, Microsoft, Programming, Site Update
Looks like it’s fixed. At least till you break something else
This has happened once or twice in the past.. usually lasting a few days. Stopping the page rendering before it finished loading would let you read most of it. I had assumed it was a problem with IE/Avant Browser, but now it sounds like some of the off site plugins like the weather indicator or the Amazon.com book gadget. What do I know, I nevef moved on to Word Press. =]
Truthfully it seems many things could of caused it. But the three big causes look to be:
• Javascript inside a table
• Conflict between Javascript libraries
• Javascript not making the WindowDom call since it was written pre-Microsft-losing-the-lawsuit (What I had)
I guess the lawsuit changed a good bit of code on how javascript had to be written. And some writers didn’t get that, since they thought the lawsuit dealt solely with embedded Video and Sound. But in “fixing that” they also broke how all javascript that works with the window has to be handled.
As a quick update today (5-23)
I swapped out the plugin that used the mootools library to a new plugin that used the built-in Prototype & Scriptlicious Libraries. So please let me know if you see any issues.
You can use defer tag
you can refer;
http://preetul.wordpress.com/2.....n-aborted/