[whatwg] <object> behavior
ian at hixie.ch
Mon Aug 31 02:08:16 PDT 2009
On Tue, 25 Aug 2009, Andrew Oakley wrote:
> 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.
Ah, yes, that's intentional (doing otherwise violates HTTP1.1). Is this
something you're forced into for compatibility?
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg