Re: XMLC, setEnableXTHMLCompatibilty

At 09:15 AM 10/7/2003 -0700, you wrote:
> >But what I see happening, is that when I generate XHTML like this:
> >
> >--snip--
> ><div>
> >        Title
> >        <div class="foo" />
> >        More content
> ></div>
> >Final Content
> >--end--
> >
> >--snip--
> >I get very different results than when I generate
> >
> ><div>
> >        Title
> >        <div class="foo" ></div>
> >        More content
> ></div>
> >--end--
> >
> >Essentially, the browser is ignoring the implcit end of the second div.
>
>Here's a relevant page from WC3 about this.
>
>http://www.w3.org/TR/xhtml1/#C_3
>
>-Justin

Ok, this is what I thought.  There never should be a <div/> or <p/>.  So, 
David, are you supplying <div/> in your tempate or are you removing the 
text node and then then XMLC's XMLFormatter is outputing <div/>???  How 
common is this?  If XMLC is doing it, then that should probably be added to 
the setXHTMLCompatibility() stuff.

BTW, what difference are you seeing in the display?  That is, what do you 
mean by "ignoring the implicit end"?  And when you say "the browser", do 
you mean IE, Mozilla, or both?

Jake