644196 - innerHTML truncates after 200 document levels when document is not XHTML

Status: RESOLVED DUPLICATE of bug 354161

(Core :: DOM: HTML Parser, defect)

Description

[Gargaj]

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0

Under Firefox 4.0, feeding a string into an element's innerHTML will cause the innerHTML to be truncated after 200 document levels if the tag isn't a standard XHTML element, even when XML is specified. This also happens with empty clolsing tags. This didn't happen in 3.x.

Reproducible: Always

Steps to Reproduce:
1. Open http://dl.dropbox.com/u/3417034/ff4test.html
Actual Results:  
The output ends with <something num="199">

Expected Results:  
The output SHOULD end with <something num="299">

This doesn't happen if the tags are changed to standard tags like "input" or "br", or if the closing tags are specified explicitly (<something num='123'/></something>)

Again, Firefox 3.x didn't have this behaviour.

Comment 1

[Gargaj]

Interestingly, after a few tests, I found the following:

<ehsk/><ehsk/><ehsk/>

becomes

<ehsk><ehsk><ehsk></ehsk></ehsk></ehsk>

When parsed, which is clearly wrong - they should be siblings in the tree, not children.

Comment 2

[Boris Zbarsky [:bzbarsky]]

> even when XML is specified.

None of your tests use XML.

> which is clearly wrong

No, that's correct parsing in HTML.  Those are unclosed tags.

I assume that all that's happening here is the tag misnesting protections from the parser kicking in.  Henri?

Comment 3

[Gargaj]

I updated the test to be valid compliant XHTML, the bug still remains - the input string already was valid XML. The browser signals it parses them in Standards Compliant Mode.

Comment 4

[Boris Zbarsky [:bzbarsky]]

> I updated the test to be valid compliant XHTML,

It's not compliant XHTML.  XHTML 1.0 says that XHTML documents can only be sent as text/html if they comply with Appendix C of that specification, which this document does not.

Or put more simply, if it's sent as text/html, then it's treated as HTML.  If you want it treated as XHTML, you need to send it as application/xhtml+xml.

Comment 5

[Henri Sivonen (:hsivonen)]

(In reply to comment #2)
> I assume that all that's happening here is the tag misnesting protections from
> the parser kicking in.  Henri?

Yeah, that should be it.