W3C home > Mailing lists > Public > www-html@w3.org > February 2001

RE: <OBJECT> tag a pain in the neck

From: Jim Correia <correia@barebones.com>
Date: Mon, 26 Feb 2001 11:39:58 -0500
To: www-html@w3.org
Message-ID: <20010226114000-f01010601-16203f66@204.107.232.110>
On 10:56 AM 2/26/01 Dave  J Woolley <david.woolley@bts.co.uk> wrote:

> > From:   Jim Correia [SMTP:correia@barebones.com]
> > 
> > On 5:52 AM 2/26/01 "NeTDeMoN" <NeTDeMoNZ@flashmail.com> wrote:
> > 
> > > Also, <object> has no autostart attribute.
> > 
> > It doesn't need one.  It is completely extensible by using param.
> > 
> > <object>
> > 
> [DJW:]  My understanding is that the user parameters are intended for
> executable objects, not for the browser itself.  In fact having
> completely extensible parameters for core media types like
> audio/basic, will simply produce a nightmare of incompatible
> implementations.

Let's look at it from a practical real world example.  You want to embed
a quicktime movie and that triggers the quicktime plug-in in your
browser.  You know that the plug-in supports autoplay, etc., when used
with embed.  You want to use object, but still pass this information
along to the plug-in.  You do it with params inside of the object tag. 
It is the right thing to do, and works in browser with working object
support.

Quoted from the W3C specification, "PARAM elements specify a set of
values that may be required by an object at run-time."  This is a
reasonable usage of same.
Received on Monday, 26 February 2001 11:39:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:15:45 GMT