[Webkit-unassigned] [Bug 68789] Unable to embed a flash plug-in using an <embed> element with mime type "application/octet-stream"

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=68789





--- Comment #12 from KishoreGanesh <kbolisetty at innominds.com>  2011-09-28 12:50:50 PST ---
(In reply to comment #11)
> (In reply to comment #9)
> > This indicates that Safari is correct (per the spec) in not loading a plug-in for the test case, since the .swf resource has a Content-Type of 'application/x-shockwave-flash' which doesn't match the specified type attribute.
> 
> It is interesting that the spec doesn't agree with Firefox, IE, and Chrome's behavior.

I am not sure, If my interpretation of the spec is correct, but I understood it like this.. When both src & type attributes are present, if type attribute specified is not supported by the plugin, then src's content type can be used to check if the plugin can handle it. src content type can determined by its extension, though the ideal mechanism to consider is the Header response from http transaction if the src url is a http.
These are the lines from the spec, that made me to arrive at the above conclusion. Please correct me if I am wrong.
====================Text from the spec=======================
Point 1:
If the element has a src attribute set

    The user agent must resolve the value of the element's src attribute, relative to the element. If that is successful, the user agent should fetch the resulting absolute URL, from the element's browsing context scope origin if it has one. The task that is queued by the networking task source once the resource has been fetched must find and instantiate an appropriate plugin based on the content's type, and hand that plugin the content of the resource, replacing any previously instantiated plugin for the element.

    Fetching the resource must delay the load event of the element's document.
Point 2:
The type of the content being embedded is defined as follows:

    If the element has a type attribute, and that attribute's value is a type that a plugin supports, then the value of the type attribute is the content's type.

    Otherwise, if the <path> component of the URL of the specified resource (after any redirects) matches a pattern that a plugin supports, then the content's type is the type that that plugin can handle.

    For example, a plugin might say that it can handle resources with <path> components that end with the four character string ".swf".

    Otherwise, if the specified resource has explicit Content-Type metadata, then that is the content's type.

    Otherwise, the content has no type and there can be no appropriate plugin for it.
==============================End================================

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.