Moderators: nickj, Lady of Mystery, Mandrake, bananafish, support
From what I've read so far, this occurs when javascript tries to access part of the DOM that hasn't been rendered yet. One way to confirm this would be to disable active scripting (Tools -> Internet Options -> Security -> Custom Level, scroll down to the bottom for active scripting) and try the problem site. If it loads without the error, re-enable active scripting and try the problem site again. If it gives the error, you've got your culprit. As for a permanent fix if that's the issue, I don't know. But that should give you enough info for others who might be more familiar with the inner workings of IE8.
Users browsing this forum: No registered users and 50 guests