Lightspark 0.7.2 not being used on Chrome

[Dennis Schridde]

On Google Chrome 27 (27.0.1444.3 (Official Build 188745) dev), Lightspark 0.7.2 is not being used. In about:plugins it is displayed in an own section - next to Adobe Flash Player where it used to be. When I playback a Flash video, Chrome uses one of the Adobe Flash Player plugins, instead of Lightspark. This worked with earlier versions of both Lightspark and Chrome (I did not test a combination of current Lightspark and <27 Chrome or the other way round.)

[Dennis Schridde (devurandom)]

P.S: In Firefox Lightspark is being used just like before (see for example bug #1158255 where I ran Lightspark 0.7.2 in Firefox 19.0.2). So I assume something changed in Chrome 27, that made it disregard this plugin.

[Antti Ajanki (aajanki)]

Try to disable all other Flash plugins besides Lightspark in chrome://plugins. Does that help?

I'm guessing that Chrome selects the Flash plugin that has highest version number, if several are installed. Lightspark currently identifies as 12.1 r720. Does the Adobe plugin have higher version number?

[Dennis Schridde (devurandom)]

Chrome used to use the Flash plugin with the highest version number, yes. But Lightspark is definitely the highest, with 12.1, while Adobe has 11.2 and Google has 11.7.

[Adam Dingle (adam-yorba)]

Here's what I think is going on:

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

As described there, Lightspark requires a newer version of the Netscape plugin API than WebKit currently supports. Lightspark 0.7.2 has NP_VERSION_MINOR = 27, and WebKit has NP_VERSION_MINOR = 24.

It would be nice if Lightspark could be compatible with older versions of NPAPI, at least recent ones.

[Stephen Ranger (sanosuke001)]

I attempted to install lightspark today (nonfree flash causes some odd graphics glitches in gdm) but chrome doesn't even load it as a plugin (not listed under chrome://plugins) even with pepperflash disabled. This is using Chrome 41.