IE, Operation aborted and MSDN

Since writing this post on DOM manipulation about a week ago msdn has crashed on me three times with the dreaded operation aborted exception.  Following Dave Reed's comment here, it looks like this is probably occurring because the call to ASP.NET AJAX's client side initialization function is too far away from the forms closing tag - causing the Sys.Application.init event to fire before the DOM is really ready (view source on one of the pages and you will see what I am talking about). Here is an excerpt from Dave's comment:

ScriptManager does not put the call to initialize in a “random” location. It is in fact, always the very last thing in the form, just before the closing form tag. There shouldn’t be anything after that (for better or for worse, form is a major part of an asp.net page), and if there is, it could only be because the dev put content after the closing form tag, and all they must do is move it inside

I found this interesting and ironic - interesting because here is an 'in the wild' example from a high-traffic site that shows what can happen if you don't wait until the DOM is ready before you start mucking with it.  And ironic because I swear I never ran into this error until after I wrote my previous post.  And of course ironic because it appears that Microsoft is misusing their own framework ;) That's it.  Enjoy!

Another Fool Proof Finish? - Question of the Week »« Mygazines Offers Full Magazine Scans Online [Free]