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: Malcolm Rowe <malcolm-www-style@farside.org.uk>
Date: Tue, 27 Jul 2004 21:43:28 +0100
To: "Andrew Fedoniouk" <news@terrainformatica.com>
Cc: "W3C Style List" <www-style@w3.org>
Message-ID: <courier.4106BE71.00000344@mail.farside.org.uk>

Andrew Fedoniouk writes:
> 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.

I read it the same thing as 'render', if we're talking about a visual UA. I 
think the change probably just reflects a greater emphasis on not assuming 
that UA = visual web browser. 

> "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.

XHTML UAs don't have to be validating UAs. 

Anyway, the XHTML spec doesn't define *when* the UA should carry out this 
validation, nor what a UA should *do* with a non-well-formed document once 
it's found one. You're assuming that it should refuse to render it, but the 
spec doesn't say that; it's not even prohibited by the XML spec. 

Received on Tuesday, 27 July 2004 16:43:45 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:14 UTC