IE Error: HTML Parsing Error

I'm trying to edit a page that I've edited a dozen or more times in the past and I'm receiving the error below. Has anyone experienced this?

I have created a blank page with OOTB "default HTML" and OOTB "freestyle div" and still get this error. Occurs when I try to edit the page, not preview and only for this one site.

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; (R1 1.1); .NET CLR 1.0.3705; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; MS-RTC LM 8; .NET4.0C; .NET4.0E)
Timestamp: Mon, 17 Sep 2012 14:52:40 UTC

Message: HTML Parsing Error: Unable to modify the parent container element before the child element is closed (KB927917)
Line: 0
Char: 0
Code: 0

Find more posts tagged with

Comments

Rick Poulin

Bwah? I suggest turning on script debugging in the developer toolbar and narrowing down the problematic script. If it has appears not to have anything to do with your customizations, it could mean that iwov has some very dumb and unsafe code that could only be rectified by support. However, given how rare it is for you and how nobody else (so far) appears to have seen this, it almost must be something trigged by your code/content. The dev toolbar should help point you in a direction...

Bowker

The script debugger is not picking anything up. The error appears but the debugger doesn't show anything (it doesn't break for this error). It appears to be something internal.

As for something in our content - this occurs when we create an empty "freestyle div" page without content (no templates, no components...)

Rick Poulin

Well, looking at Microsoft's listed KB article, this could very well happen if iwov's code does the stupid violation, and the script happens to execute before the browser has seen the closing tag for the parent container. An empty freestyle page would be the most likely candidate to produce this, since it would be lighter on Javascript than fixed layout and any page with components on it.

Sounds like a support case to me.

Bowker

already opened a case.

Bowker

We had added Modernizr.js (do a google search if you are unfamiliar with this) and it was causing the issue.

Samir_Friend

We had added Modernizr.js (do a google search if you are unfamiliar with this) and it was causing the issue.

This is awkward. We've used modernizer before with 7.2.1 and it's wasn't an issue. Probably there might be some other related libraries which you need to include with modernizer which should stop it from breaking the pages.