> Hi,

> My NPAPI-based plugin fails to load on Macintosh Chrome.

> Chrome loads the Extension from the Webstore ("LightUp for Macintosh") and
> *does not complain* but it fails to show in navigator.plugins[]

> It used to work just fine and I haven't changed anything, so how do I get
> Chrome to display some debugging info as to why it shows the Extension but
> is obviously not loading it.

> If I install it for Safari (/Library/Internet-Plugins), Chrome picks it up
> and fine and it works.  So the plugin is fine, its just some meta-data
> requirement that appears to have changed.

> Any ideas?

>   Adam

> Just FYI Adam, NPAPI will soon be deprecated in Chrome extensions.  I
> heard they plan to stop supporting it in favor of Pepper/PPAPI. Just so you
> know.  I chose not to use NPAPI due to this.

> James

> On Wednesday, November 14, 2012 12:42:02 AM UTC-8, Adam Billyard wrote:

>> To answer my own question for the record:

>> commandline arg "--debug-plugin-loading"  helped track down that the
>> Bundle wasn't being created

>> The reason is that the limited docs on the manifest.json implied the
>> plugins[] field should be a single file, not the entire .plugins folder

>>   Adam

>> On Tuesday, 13 November 2012 17:27:15 UTC, Adam Billyard wrote:

>>> Hi,

>>> My NPAPI-based plugin fails to load on Macintosh Chrome.

>>> Chrome loads the Extension from the Webstore ("LightUp for Macintosh")
>>> and *does not complain* but it fails to show in navigator.plugins[]

>>> It used to work just fine and I haven't changed anything, so how do I
>>> get Chrome to display some debugging info as to why it shows the Extension
>>> but is obviously not loading it.

>>> If I install it for Safari (/Library/Internet-Plugins), Chrome picks it
>>> up and fine and it works.  So the plugin is fine, its just some meta-data
>>> requirement that appears to have changed.

>>> Any ideas?

>>>   Adam