W3C home > Mailing lists > Public > public-html@w3.org > June 2009

Re: <object> element - Global Attributes

From: Michael A. Puls II <shadow2531@gmail.com>
Date: Sat, 13 Jun 2009 19:46:45 -0400
To: "Ian Hickson" <ian@hixie.ch>, "Joe D Williams" <joedwil@earthlink.net>
Cc: "Boris Zbarsky" <bzbarsky@mit.edu>, "HTML WG" <public-html@w3.org>
Message-ID: <op.uvhln7d81ejg13@sandra-svwliu01>
On Sat, 13 Jun 2009 19:32:44 -0400, Ian Hickson <ian@hixie.ch> wrote:

> On Sat, 13 Jun 2009, Joe D Williams wrote:
>>
>> attribute @classid is listed in the sequence for "the user agent must
>> run the following steps to determine what the object element represents:
>> ... " but not in the listing of <object> element Global attributes or
>> DOM interfaces.
>
> Right, that's intentional. It's not a conforming attribute, you're not
> supposed to use it, but we have to define what happens when someone does
> anyway.

Is there any news as to whether IE.next will map @type to @classid (and  
then @data to the appropriate param) for plugins for <!DOCTYPE html> pages  
so authors don't have to use IE conditional comments (where the markup in  
them isn't checked by the validator) or invalid markup?

For some plugins, you can get things working in IE without @classid, but  
not all. And, if IE still requires classid, it's going to be a pain still  
to use <object> for plugins and support IE.

In other words, is the IE team O.K. with @classid being invalid, or is it  
a showstopper?

@Chris?

-- 
Michael
Received on Saturday, 13 June 2009 23:47:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:38 GMT