Maybe OT: Content Disappears when cfm call, shows when html

I've had that same experience attempting xmlParse -- the trim was absolutely necessary. This was just a plain 'ol XHMTL document. Not strict XML. >> > I believe according to the standard, XML isn't allowed to have any white >> > space before the doctype. This is the first I'd heard of a browser >> > refusing to render it though. >> >> Actually IIRC, the XML standard does not care about white space, nothing >> else is allowed before the doctype, but whitespace is ok. >> >> I.E. on the other hand has a different opinion. > > Well that's what I'd remembered reading... and at the time I was trying > to figure out why a particular XmlParse(variable) wasn't working... > turned out XmlParse(trim(variable)) was the fix, because the parser was > choking on white space before the document root element (there wasn't a > doc type in that particular packet). And since then I've always been > sure to trim() before using XmlParse because of that. This is the first > time I can recal anyone disagreeing about the white space, although I > would personally have loved for the standard to insist that the parser > be able to handle white space there.