[whatwg] <object> behavior
andrew at ado.is-a-geek.net
Tue Aug 25 01:40:37 PDT 2009
Ian Hickson wrote:
> I'm not sure exactly what change you mean. The spec already has some of
> Gecko's behaviour (in particular the special-casing of certain MIME types
> to enable sniffing), are there other changes you think we should include?
Boris Zbarsky wrote (near the top of this thread):
> If the type attribute was set to something that parsed as a MIME
> type, and if that type would be handled by a plug-in (that is, we
> have a plug-in to handle it, and have no other method for handling
> it), then use the type attribute's type instead of the header type.
So if we had a type attribute of application/x-shockwave-flash, and a
Content-Type header of image/png we would use the flash plugin.
Following the HTML5 spec we would use the image renderer.
>> I'm also confused about the criteria for creating a nested browsing context.
>>> - If the resource type is an XML MIME type
>>> - If the resource type is HTML
>>> - If the resource type does not start with "image/"
>> Does that mean:
>> - xml_mime_type OR html OR not_image
>> this is the same as xml_mime_type OR not_image
>> - xml_mime_type AND html AND not_image
>> this would be application/xhtml+xml, application/ce-html+xml etc. but
>> *not* text/html
>> - (xml_mime_type OR html) AND not_image
>> makes sense but would certainly need clarification in the spec
> The former. I've added an "or" and removed the (redundant) HTML line to
> make this clearer.
More information about the whatwg