Just pushed the latest update to ReadPath and noticed that I started getting weird errors in IE. The problem actually happened in both IE6 and IE7 which made me worry a bit more than usual. I had made a couple of changes prior to this happening, so it was time to start tracking down which change caused the problem.
First off, I had been playing with YSlow and working on getting the pages optimized for speed and cacheability. I had been appending random param strings to the JS includes so that IE wouldn’t cache it. At the time it was just too much of a hassle to try and determine if the problems I was seeing were due to bad code or just old code. So now that things were settling down a bit I pulled those params out. This meant that IE would start caching JS files.
Second, I started using the YUI libraries for a lot of the UI widgets. These really make it easier to develop a web application and it’s truly amazing how well they work across all of the major browsers. Web application development has come light years from where it was just a short time ago.
With these changes, I booted up my Win2k VM with IE6 and found that I was now getting “Operation Aborted” errors in IE. The page wouldn’t load at all and there was no way to determine what was causing the problem. So off to Google I went and quickly came across this solution.
This error occurs because
3. IE thinks its illegal to do the above operation and throws up the error.
So the solution, which YUI already recommends is to wrap your initilization code in:
This causes its own problem of course. The pages on ReadPath have a fair number of dialog boxes that are rendered by the YUI library and then hidden until they’re needed. With the new way of handling the initialization code, Firefox renders the unformatted dialogs for a brief amount of time before the page has finished loading. This causes a really ugly loading effect.