- From: Chris Lilley <chris@w3.org>
- Date: Tue, 27 Jul 2004 09:54:39 +0200
- To: "Andrew Fedoniouk" <news@terrainformatica.com>
- Cc: "Henri Sivonen" <hsivonen@iki.fi>, www-style@w3.org, "L. David Baron" <dbaron@dbaron.org>
On Tuesday, July 27, 2004, 9:51:36 AM, Andrew wrote: AF> ----- Original Message ----- AF> From: "Henri Sivonen" <hsivonen@iki.fi> AF> To: "Chris Lilley" <chris@w3.org> >> > Where does it say in the XHTML spec that incremental display must be >> > disabled for that media type? >> >> Nowhere. It is an just unimplemented feature in those browsers. >> AF> Strictly speaking, XHTML parser (UA) must read </html> to decide if AF> document well-formed (valid) or not. And you further claim, presumably, that it must wait for this closing tag, thus precluding incremental rendering. This is incorrect. The parser is required to go into error when it finds the document is not well formed. It is not required to buffer up the entire document before doing anything else. Indeed, a popular parsing method (sax) does the exact opposite, firing a stream of events as the document arrives, and is ideally suited to incremental rendering. AF> And only ather that render document as it *must* be well-formed [1]. Please point to a specification that requires this chronological sequence. AF> This the end of era of incremental rendering... No, it isn't. AF> [1] http://www.w3.org/TR/xhtml1/#h-4.1 AF> Andrew Fedoniouk. AF> http://terrainformatica.com -- Chris Lilley mailto:chris@w3.org Chair, W3C SVG Working Group Member, W3C Technical Architecture Group
Received on Tuesday, 27 July 2004 03:54:58 UTC