Re: Adopting WHATWG work as a base for work by the new HTML working group (was Re: HTML5 script start tag should select appropriate content model according to src)

Quoting David Dorward <david@dorward.me.uk>:

>> <embed> is much more interoperably implemented for embedding media
>> that requires plugins.
>
> Vendors seem to be waking up to standards, perhaps it is about time they
>  implemented object better.

Patricularly now that most browser vendors are represented on the  
WHATWG, it would be the perfect time to see if object can't be  
implemented in a saner kind of way.

Admittedly I haven't looked into what the implementation issues with  
object are that were hinted at before, but naively I would have  
thought that it would be possible to get plugins to expose their API  
in a consistent way and then allow browsers to hook into those via the  
object? i.e. get standardisation of interfaces at plugin level, after  
defining a superset of interfaces that are expected at browser level?

P
-- 
Patrick H. Lauke
______________________________________________________________
re·dux (adj.): brought back; returned. used postpositively
[latin : re-, re- + dux, leader; see duke.]
www.splintered.co.uk | www.photographia.co.uk
http://redux.deviantart.com
______________________________________________________________
Co-lead, Web Standards Project (WaSP) Accessibility Task Force
http://webstandards.org/
______________________________________________________________
Take it to the streets ... join the WaSP Street Team
http://streetteam.webstandards.org/
______________________________________________________________

Received on Thursday, 26 April 2007 08:04:06 UTC