User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030507 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030507 when opening an xml file all tags and data nested more then 28 levels deep don't show up. No indication of this is given either. in my case the data was being generated on the server and it was some time before I realized the data was being truncated by mozilla and not the server. Reproducible: Always Steps to Reproduce: 1. 2. 3.

expected all 31 tags and hello world to show up in browser. instead mozilla stops at 28.

The content is still there according to DOM Inspector, so this looks like a layout bug. Reassigning.

Hmm.. that's actually about 200 levels of nesting there (the prettyprinter ends up generating nested <div>, <table>, <tr>, <td> tags for each tag in the original markup and that produces a block, table-outer frame, table-inner frame, rowgroup frame, row frame, cell frame, anonymous block frame). I'm pretty sure that this is running up against layout's stack overflow protection... That's set at 200 levels on non-Mac systems and 75 on Mac. There's not much to be done here short of not generating such a deep DOM and frame tree (if we didn't cut frame construction off there, we would be crashing instead as we overflowed the stack).

The reason i created the <div><table><tr><td> was to get the +/- thing next to the elements, but let the element-text not wrap below the +/-. I.e. i want something like this: +-------- screen ---------+ | | + <elementName foo="bar" bar="foo" bin="big" hi="hello" If anyone can write up some css that does that (and the '+' still needs to be clickable) then it'd be easy to rewrite the XSLT stylesheet that prettyprint uses.

Something like this perhaps... all tables were removed, this takes us from a maximum frame depth of 206 to 97 for the attached testcase. I used <div><span><div> for the nesting, the last <div> is only needed for what I suspect is an IB bug - if I exclude the last <div> and toggle the <span> between display:none/block like I wanted, then the text node that follows is still on a new line.

*** Bug 304493 has been marked as a duplicate of this bug. ***