W3C home > Mailing lists > Public > public-html@w3.org > August 2008

Re: HTML5 object element - classid or not classid?

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Mon, 04 Aug 2008 10:49:33 -0400
Message-ID: <489716FD.1070206@mit.edu>
To: "Dr. Olaf Hoffmann" <Dr.O.Hoffmann@gmx.de>
CC: public-html@w3.org

Dr. Olaf Hoffmann wrote:
> For object currently these element specific attributes are
> defined:

This is the section that describes what documents are conformant to 
HTML5, yes?

> Later in the text some attribute 'classid' is mentioned:

In the section that describes how UAs are to handle <object>, right?

How is this different from any other case where there are authoring 
conformance requirements?  In all such cases UAs need to know what to do 
with web pages that violate said requirements (in this case by adding a 
'classid' attribute).

> If there is an attribute 'classid', it should be obviously
> defined and the purpose of this additional attribute should
> be explained to the audience including an explanation
> of its possible values or are this the same values as for
> 'data' as in HTML4?

This attribute was present in HTML4 and its behavior only needs to be 
defined to handle legacy content.  Authors of HTML5 documents must not 
(in RFC terms) use it if they want to claim conformance.  UAs must (in 
RFC terms) do certain things with it to claim conformance.

> (by the way, why is 'declare' missing, this sounds
> pretty helpful to start objects without the need of 
> scripts or internal controls in the referenced object?)

Probably because no one actually implements it?

Received on Monday, 4 August 2008 14:52:16 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:36 UTC