W3C home > Mailing lists > Public > www-html@w3.org > June 2005

Re: [XHTML 2] 24.1 OBJECT declare and "completed loading" (PR#7751)

From: Henri Sivonen <hsivonen@iki.fi>
Date: Wed, 1 Jun 2005 16:37:20 +0300
Message-Id: <80f28c5f36afe9593e61f4dd8e938c85@iki.fi>
Cc: "Jim Ley" <jim@jibbering.com>, <xhtml2-issues@mn.aptest.com>, <w3c-html-wg@w3.org>, <www-html@w3.org>
To: "Brad Pettit" <bradp@microsoft.com>

On Jun 1, 2005, at 04:25, Brad Pettit wrote:

> What if the Xhtml document is not well-formed?

In an incremental implementation, the processing the doc would halt 
upon discovering the first fatal error.

> Even a non-validating Xml parser is required to check for 
> well-formedness before determing whether
> the document is xml:
> http://www.w3.org/TR/2000/REC-xml-20001006#sec-conformance

A non-validating parser may optimistically start treating a document as 
XML before it has seen the full doc. The application is free to act on 
the data provided by the XML Processor before the XML Processor has 
seen the full doc. The XML spec only says that the XML Processor MUST 
NOT continue reporting data to the app after a fatal error has been 

> Document well-formedness -- or the lack thereof -- might not be
> determined until the end of the content is reached. Is it wise to be
> executing <object> elements -- particularly those that reference code
> external to the browser -- as they are encountered during the process 
> of
> loading a potentially incomplete or incorrect document?

I don't think it is necessary to refrain form acting on <object>s ASAP 
in an incremental implementation.

Henri Sivonen
Received on Wednesday, 1 June 2005 13:37:29 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:06:10 UTC