Perhaps there is something that I don't understand here but just in case here is a bug. The &nbsp; entity does render in HTML but does not render properly in XML (instead I see "nbsp" -- no ';' and no '&') Here is a sample snippet which has an nbsp in the legend as well as in a paragraph. <?xml version="1.0"?> <window xmlns:html="http://www.w3.org/TR/REC-html40"> <window xmlns:xul="http://www.mozilla.org/keymaster/gatekeeper/ there.is.only.xul"> <?xml-stylesheet href="unified.css" type="text/css"?> <!DOCTYPE window> <window> <html:fieldset><html:legend> &nbsp; Dimensions &nbsp; </html:legend> <html:p/> some text with an &nbsp; in the middle of it. </html:fieldset> <html:p/>the end </window>

Change platform and OS to ALL since cmanske@netscape.com ran into this problem on Windows.

This is a legitimate bug, but it's not the parser. The entity token is being correctly generated for the &nbsp;'s. However, my guess is that the reflow/rendering code is not treating them like entities.

Last I checked P1 meant crasher...Reduing priority to P2. Also: your XML is malformed - you have 3 open window tags and only one close tag. Why is this being allowed by our xml parser?

Well, I fixed it so that the xml-content-sink now supports entities just like the html content sink does. However, I don't know if xml supports the same set of entities that html supports so there may be work required by the xml parser. I'm reassigning this to vidur to deal with that issue and maybe replicate the code in the xul content sink?

&nbsp; is not a valid entity in XML, from what I can tell. When we switch over to James Clark's parser, it will generate an error since &nbsp; is not a declared entity.

"rubber stamping" verified invalid...vidur, can you really VERIFY INVALID this bug.

marking verified per developers input.