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

Re: <object> element

From: Joe D Williams <joedwil@earthlink.net>
Date: Tue, 2 Jun 2009 09:54:11 -0700
Message-ID: <0F0D88D5EC9B41DAA9C7D7CEE50A8777@joe1446a4150a8>
To: "Boris Zbarsky" <bzbarsky@MIT.EDU>
Cc: "HTML WG" <public-html@w3.org>
Hi Boris,

>>> It'd be really nice if plug-in registration registered q values in 
>>> addition to types, but that's not a web-facing issue, of course...
>>
>> Maybe more about q value is in order (like, how does it help?) ... 
>> .
>
> A q value would change the information the browser gets from the 
> plug-in about a MIME type from a binary value (support or not) to a 
> decimal value in the 0-1 range indicating how supported it is...  So 
> a plug-in could indicate "yeah, I can handle this MIME type, but not 
> very well" kind of things.  Not really related to HTML, but to the 
> internal APIs browsers use to talk to plug-ins.

That is interesting. Authoring and Delivery ratings?
I can see how a plugin might rate itself but how does the content 
declare how complex it is? For instance X3D has statements to tell 
level of capability required but the player doesn't know this until it 
loads the file and looks at some properties. Likewise the plugin can 
report its capabilities but you must ask some specific questions when 
it is already running. If the plugin fails or declines then it is 
probably late for the <object> fallback so recovery may get 
complicated. Actually the data in the content file are "Profile" that 
tells the basic level of features ranging from Interchange to Full, 
and "Component", like H-Anim, that brings in other structure and 
capabilities. But the plugin cannot report until it is running and the 
file info is not visible to the player until the file is loading.

Thanks and Best Regards,
Joe
Received on Tuesday, 2 June 2009 16:54:55 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:04 UTC