[Webkit-unassigned] [Bug 36667] Plugin versions are not propagated to navigator.plugins

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Jun 19 21:58:45 PDT 2014


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


Bruno R. <bruno at hexanet.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bruno at hexanet.net




--- Comment #5 from Bruno R. <bruno at hexanet.net>  2014-06-19 21:59:05 PST ---
(In reply to comment #4)
> It doesn't really make a lot of sense to only implement this for Chrome, but expose an always empty version string in every other WebKit-based browser. It can be challenging to implement this property on all platforms at once, but something needs to be done to solve this. Personally, I'd try to fix as many platforms as I can, then hide the IDL attribute behind an #if check for others.

Any progress on this?

No webkit browsers currently expose plugin.version at the moment, which is quite bad from a cross-browser standpoint now that IE11 does.
http://msdn.microsoft.com/en-us/library/ie/dn268316(v=vs.85).aspx

While it is possible to get an roughly accurate version most of the time from plugin.description or plugin.name, versions don't always match properly between Firefox/IE and Webkit/Blink for all plugins.

> Firefox seems to use CFBundleShortVersionString. Is this what Chromium uses to populate this field in PluginData? Where does it come from for unpackaged plug-ins?
Apparently yes as per this question's statement:
http://stackoverflow.com/questions/16979253/installed-plugin-version-not-showing?rq=1

For more perhaps useful info as far as implementation, see: https://bugs.launchpad.net/pipelight/+bug/1313457

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



More information about the webkit-unassigned mailing list