plugin not working on Chrome

[ji32...@gmail.com]

Hey - awesome plugin!

It works well on firefox but not chrome.

I've tried the provided crx, compiling the code, exe install....  nothing works..

Chrome says: could not load Activex hosting plugin for Firefox.

What is the cause of this?  

does it need to be built \ installed \ embedded in a specific way to make it work in chrom?

Thanks for your help!

[Leeor Aharon]

There's nothing special needed for Chrome, other than packaging it as a .crx package. Here at CloudShare we are installing it via the Chrome App store, but at the very least, I think you should be able to drag and drop the .crx file onto the extensions tab while it's open.

Maybe it has to do with how you are signing the package/DLL? Doesn't Chrome provide any additional info in some console/log? Is the failure during the package installation? Or when trying to use the plugin from a web page?

Leeor.

--
You received this message because you are subscribed to the Google Groups "ff-activex-host" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ff-activex-ho...@googlegroups.com.
To post to this group, send email to ff-acti...@googlegroups.com.
Visit this group at http://groups.google.com/group/ff-activex-host?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[ji32...@gmail.com]

Hi - thanks for the quick response!

I can install the crx or as an unpacked extension - no error. The error is only when I load the webpage.

It's my first time playing with Chrome extensions so I may have missed something very basic - do I need to sign the extension\DLL? currently it's not signed.

Still, that wouldn't explain why the crx downloaded from the project doesn't work.

Could it be something to do with the ActiveX? - does that need to be signed?

Thanks again for your help!

[ji32...@gmail.com]

ok, I think I've found the problem

in NP_GetEntryPoints there is a condition (pFuncs->size < sizeof(NPPluginFuncs)

It seems that Chrome passes a structure with size 80, while the expected size is 84

Commenting the lines with that condition seems to make it work in Chrome but I don't know what side-effects it might cause.

Also, if this issue is a result of Chrome behaviour I would expect it to impact every plugin - so it's interesting that the plugin does work for you. Perhaps there is some Chrome or compile setting that is different?...

Looks like it is working now, but I'd be interested to understand the root issue (and avoid side effects...)

Any thoughts?...

[Leeor Aharon]

Interesting.

I seem to remember having issues with that condition in the past, but I can't remember the specifics (which browser, and the size it was passing).

The plugin doesn't need most of the functions in that structure, and those which are needed are placed at the start of the structure (IIRC), so the important thing is simply not to copy past the end of the structure.

Leeor.