W3C home > Mailing lists > Public > www-style@w3.org > July 2004

Re: XML incremental rendering, was Re: Standards mode and Quirks mode (was Re: [CSS21] Test Suite)

From: Andrew Fedoniouk <news@terrainformatica.com>
Date: Tue, 27 Jul 2004 13:24:58 -0700
Message-ID: <005401c47417$ca4efae0$eb01000a@AFedoniouk>
To: "Malcolm Rowe" <malcolm-www-style@farside.org.uk>
Cc: "W3C Style List" <www-style@w3.org>

Thanks, Malcolm,

See: If a user agent encounters an element it does not recognize:

XHTML: "must process the element's content."
HTML:  "should try to render the element's content"

It is not exactly same thing - HTML will try to render, XHTML will process -
I have no idea what this "process" means here.

And in the link you provided:

"In order to be consistent with the XML 1.0 Recommendation [XML], the user
agent must parse and evaluate an XHTML document for well-formedness. If the
user agent claims to be a validating user agent, it must also validate
documents against their referenced DTDs according to [XML]. "

Actually this is even more strict: in general validation against DTD could
not be done on partial content.

Andrew Fedoniouk.
http://terrainformatica.com


From: "Malcolm Rowe"
> > HTML, at least, has :
> > "If a user agent encounters an element it does not recognize, it should
try
> > to render the element's content."
> > [http://www.w3.org/TR/html401/appendix/notes.html#h-B.1]
> > This statement allows to render non valid documents e.g. having
non-closed
> > </html>
> >
> > XHTML does not have nothing close and no mentioning about partial
content
> > at all.
>
> That's got nothing to do with partial content, it's about processing
> unrecognised elements.
>
> XHTML has "If a user agent encounters an element it does not recognize, it
> must process the element's content.". Same thing.
> http://www.w3.org/TR/xhtml1/#uaconf
>
Received on Tuesday, 27 July 2004 16:25:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:31 GMT