Re: [jsr-314-open] [xmldecl-696] suppressing XML declaration for MR1

Oh, I forgot one use case. Max was saying that they need to use CDATA in their templates, but the CDATA should not be sent to the browser. So there is the same problem with CDATA as with the XML declaration. -Dan On Fri, Dec 11, 2009 at 6:38 PM, Dan Allen <dan.j.allen(a)gmail.com&gt; wrote: > On Fri, Dec 11, 2009 at 6:30 PM, Jim Driscoll <Jim.Driscoll(a)sun.com&gt;wrote: > >> Oh, THAT's what he meant. He tried to describe the problem to me, but >> our discussion got cut off. I've even run into this with demos - it's >> actually a pretty big deal, I think. >> > > +1 > > >> >> Fortunately, the declaration is optional, as I understand the XML >> standard. >> > > Right, but from what I understand from Max, tooling is adding it > aggressively and it becomes a fight between developer and tool to leave it > off. He could probably speak to this more. > > >> >> As for "some browsers", let's just name it: IE. The XML declaration >> triggers their "I don't care about your mime-type, I know better than you" >> code. Though it wouldn't be surprising if it triggered some quirks-mode in >> other browsers. >> > > Yep, pretty much. > > -- > Dan Allen > Senior Software Engineer, Red Hat | Author of Seam in Action > Registered Linux User #231597 > > http://mojavelinux.com > http://mojavelinux.com/seaminaction > http://www.google.com/profiles/dan.j.allen > -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action Registered Linux User #231597 http://mojavelinux.com http://mojavelinux.com/seaminaction http://www.google.com/profiles/dan.j.allen