IE’s KB927917 Error

I’m currently working on a web application and am trying to take advantage of the ASP.NET AJAX framework (which I think is kinda weak is comparison to some other frameworks, but I digress).

I was attempting to use the modal pop-up control, but the framework is apparently manipulating a node in the DOM before it has been closed. If you check out Microsoft’s support page, you’ll notice that they don’t have any real solutions - only workarounds. Lame.

Unfortunately, none of these workarounds are feasible given the current environment in which I’m working so I’m having to essentially create my own modal pop-up. If you’ve got experience with this issue and have come up with a solution (versus a work-around), please leave a comment.

Edit June 5, 2008: Commenter tbela99 suggested verifying that all of your existing XHTML is well-formed (with no closing tags). This is always a step that should be done prior to releasing; however, it’s a difficult thing to do whenever you’re adding functionality to a project that has already been released. tbela99 made a couple of additional suggestions that are more JavaScript oriented, as well - check out the comments.


This entry was posted on April 23rd, 2008 and is filed under Development. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response or Trackback from your own site.

 
« Using the LG Voyager as a Smartphone
Contributing to Slideshow JS »
 
 

2 Responses to “IE’s KB927917 Error”

  1. tbela99
    5. June 2008 at 06:27

    i’ve got this problem too. first of all check your XHTML code is well formed (no unclosed tag)

    and at the second time use the dom loaded event to trigger all your scripts that modify dom, you can see implementation of the dom loaded in libraries such as
    prototype.js:
    document.observe(’dom:loaded’, function () { /* your script goes here */ }),
    mootools:

    document.addEvent(’domloaded’, function () { /* your script goes here */ })

    jquery:
    jQuery(document).ready(function () { /* your script goes here */ })

    I used the second method (dom loaded event) and it worked fine until the day the same error happened, I wonder and try to find out what was going wrong. after validating the content I discovered an unclosed tag. I solved this problem and anything is fine now

  2. Tom
    5. June 2008 at 06:38

    Hey,

    Thanks for the suggestion - this was actually something that I had not thought about.

    The downside of integrating a new control with an existing project (that’s actually composed of a bunch of other controls) makes it difficult to fully be aware of other developer’s implementations.

    I know this particular post tends to get a lot of hits so I’ll be sure to edit the post and include your suggestions.

    Tom

Leave a Reply