W3C home > Mailing lists > Public > public-html@w3.org > April 2014

Re: Proposed change to spec on object tag

From: Simon Pieters <simonp@opera.com>
Date: Mon, 28 Apr 2014 10:10:13 +0200
To: "Davis, Greg" <greg.davis@pearson.com>
Cc: "Charles McCathie Nevile" <chaals@yandex-team.ru>, "public-html@w3.org" <public-html@w3.org>
Message-ID: <op.xe0ozbifidj3kv@simons-mbp>
On Fri, 25 Apr 2014 17:21:21 +0200, Davis, Greg <greg.davis@pearson.com>  
wrote:

> Really!? Could you expand on this? I wasn't aware that it was currently
> possible... seems like a silly conversation if I can already do it :)

I meant, what you described is a proposed solution to some problem, but  
you didn't describe the problem well before going ahead and proposing a  
solution. This makes it impossible for others to evaluate the proposal.

>  Wow... obviously I'm ignorant on what you can do with the object tag...  
> if
> I told you how many hours I'd spent trying to figure this out :-(

I meant that you can implement your proposal in JS today. You can access  
the parent <object> element using window.frameElement, and from there you  
can iterate over the <param> elements. To make an <object> element fall  
back, you can add a classid attribute with a bogus value, or remove the  
classid/type/data attributes. If you want to do that when some script  
fails to compile or fails to catch an exception, use window.onerror.


>> Can you point to some concrete examples that would benefit from your
>> proposal?
>>
>> FWIW, <object> is so complicated already because it does too many
>> different things that we've tried to avoid extending it and are still
>> struggling with interoperability, so it may be hard to convince  
>> browsers to
>> complicate it further.
>
>
> So does it stand as a tag to avoid for the use I'm describing then?

I'd still like to understand better what the use is, exactly.

> We've
> been having conversations at the IDPF (standards org for ePubs) about  
> this,
> and everyone in the group favored using object tags if they "worked
> better", but now I'm feeling like we are all victims of a lack of
> documentation... and if everything I'm saying is doable same-origin, then
> it would work fine as described right now, since everything in an ePub is
> same origin.

OK.

-- 
Simon Pieters
Opera Software
Received on Monday, 28 April 2014 08:10:47 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:38 UTC