© 2009 . All rights reserved. browser-share-screen-shot

technical glitch

Today I begin ripping apart my blog to see why IE7 gives an “aborted operation” warning every time you try to open the comments. Please stand by.

I’d like to thank Brian Gardner, part of the team at Revolution, who sent me the original code to work with.

Update: The Answer

The answer is there is no answer, er, no solution that is. I read all of the following articles before I found out what was happening:

No one had a definitive answer. Finally got the scoop at http://news.softpedia.com/:

One error message that plagued Internet Explorer 7, but that won’t make it into the final version of Internet Explorer 8 refers to “operation aborted” messages. In IE7, operation aborted errors, marked by the associated dialog box featured in the screenshot on the left, prevented users from surfing certain websites, serving navigation error screens instead. IE7 simply failed to offer any way around the error, preventing the accessing of specific websites affected by a HTML parsing bug. However, with the next iteration of the Internet Explorer browser, end users will no longer face the operation aborted dialog box, starting with IE8 Beta 1.

I unplugged all my plugins. I removed all my widgets. I deleted the old template and uploaded a brand new copy. Nothing worked. I fucking hate IE7. But there is an inescapable fact…

browser-share-screen-shot

So I’ll just have to quite using embedded video for a while till I find the real solution.

9 Comments

  1. Posted 14 Jan ’09 at 14:09 | Permalink

    You could send out a crack team of Blackwater types to force everyone to not use IE.

  2. Posted 14 Jan ’09 at 14:52 | Permalink

    i have no idea why folks don’t switch to firefox. i know that there are issues- i haven’t personally had any of them. it’s secure and works beautifully every time i boot up. internet explorer sucks all the way ’round.

  3. Posted 14 Jan ’09 at 15:02 | Permalink

    Hi, i got this link cause you quoted one of my posts.

    The solution ( Strange? ) Is simply put the flash content inside a div.. If this will not work Add a div..

    :) Bye Baccega Andrea

  4. Posted 14 Jan ’09 at 16:50 | Permalink

    The answer is there is no answer, er, no solution that is.

    The answer to the ultimate question of life, the universe, and everything is… 42!

    Agis last blog post..jaydiohead is in the house

  5. Posted 15 Jan ’09 at 01:36 | Permalink

    IE7 has some real “issues” with objects. Things must be in constrained boxes or it can’t handle them.

    Putting embeds in their own area with div tags might solve the problem, but you have no guarantees as to what the CSS will do with the tags.

    I have to tell some lies to get my img tags to work predictably, so that may be all that’s necessary.

    Bryans last blog post..For Harry Potter Fans

  6. Posted 15 Jan ’09 at 12:28 | Permalink

    IE7 emerged just as I was finishing a large AJAX-based project for a client. The product worked fine in every other major browser… including IE6… but some sort of timing anomaly caused frequent failures in IE7. We found a workaround without ever understanding the cause. IMHO, IE7 sucks, and not just a little bit.

    Steve Batess last blog post..FISC F^cks Folks

  7. DBK
    Posted 15 Jan ’09 at 15:46 | Permalink

    What up, bro’? Warm greetings from a very cold place (Minnesota).

  8. Posted 15 Jan ’09 at 16:03 | Permalink

    It’s 7 degrees here and I haven’t the will to do anything but hibernate. When you going to get back to blogging old man?

  9. Posted 16 Jan ’09 at 17:35 | Permalink

    Hey, DBK! Come back to blogging! You were always a voice of sanity… and snark, of course…

    Steve Batess last blog post..R.I.P. John Mortimer, Andrew Wyeth