[Webkit-unassigned] [Bug 20267] Crash on some pages due to a plugin

[bugzilla-daemon at webkit.org]

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


zuh at iki.fi changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |zuh at iki.fi




------- Comment #3 from zuh at iki.fi  2008-08-21 02:15 PDT -------
(In reply to comment #2)
> The patch will skip over mime descs that have fewer than three elements while
> the version in PluginPackageWin looks like it will continue successfully if
> there is no description or extension list -- maybe this patch should be
> modified to cater for that condition too?

I wonder if that's a common or legal practise...

I suppose omitting description would be tolerable, but what's the functionality
if you don't specify extensions? Does it mean '*' implicitly? I couldn't find a
good source of information on how the mime types actually should be handled.

Mozilla's docs just state the three fields, claim that the separator is ';'
instead of ':' and do not mention omitting them:

http://developer.mozilla.org/en/Gecko_Plugin_API_Reference/Plug-in_Development_Overview#Unix

The other place where I could find mention of the format is here:

http://gplflash.sourceforge.net/gplflash2_blog/npapi.html#SEC9

but the only difference is that there the format seems to match what is really
used.

I'd hesitate to allow badly formatted mime descriptions just based on the win
port allowing it. After all, it's not too hard  to return 'my/mime::" instead
of just "my/mime"... Though if "my/mime:*:" is equal in functionality to
"my/mime", I see no point disallowing it either.

So I'll gladly remake the patch for that but I'd first like to hear a good
reason for it ;)


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