W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2004

XHTML rendering and media types (Was: Re: [whatwg] Seperation of Content and Interface)

From: Max Romantschuk <max@provico.fi>
Date: Thu, 19 Aug 2004 14:33:04 +0300
Message-ID: <41248FF0.5020703@provico.fi>
Matthew Raymond wrote:
>    As I explained before, it is my understanding that a compliant XHTML 
> renderer will not display a page with invalid markup. IE6 is so "good" 
> at rendering XHTML because it does not parse or render it as XHTML at 
> all. Effectively, you're saying that Mozilla would be so much better if 
> it rendered XHTML as tag soup.

I'm not sure how IE handles this, but a compliant browser should render 
XHTML in one of two ways:

When the XHTML is labeled as text/html a traditional SGML parser should 
be used, and the document should be compliant with Appendix C of the 
XHTML spec: http://www.w3.org/TR/xhtml1/#guidelines

When the XHTML is labeled as application/xhtml+xml as defined by RFC 
3236 ( http://www.ietf.org/rfc/rfc3236.txt ) an XML renderer should be 
used. In this case I would assume that rendering before the entire 
document is recieved is backwards, as an invalid document should not 
render at all.

More details on XHTML media types can be found here:
http://www.w3.org/TR/2002/NOTE-xhtml-media-types-20020801/

.max

-- 
Max Romantschuk
http://max.nma.fi/
Received on Thursday, 19 August 2004 04:33:04 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:36 UTC