How to enable npapi plugins which are placed in "page-worker" page of Firefox extension?

[powentan]

Hi all,

Since Firefox 26 has decided to set "click to play" plugin by default, I have encountered a enabling plugin problem.

If the plugin is placed in the web page, either visible plugin or invisible plugin has a chance to enable it while navigating to that web page.

However, in my case, my plugin is placed in the extension's "sdk/page-worker" page, so there is no chance for the user to enable it unless I open the "page-worker" page(resource://...) purposely.

I think it will not be a good solution to open extension's page to let the user activate plugin.

Is there any good solution for my situation?

Thanks.

Powen

[p***@gmail.com]

Post by powentan
Hi all,
Since Firefox 26 has decided to set "click to play" plugin by default, I have encountered a enabling plugin problem.
If the plugin is placed in the web page, either visible plugin or invisible plugin has a chance to enable it while navigating to that web page.
However, in my case, my plugin is placed in the extension's "sdk/page-worker" page, so there is no chance for the user to enable it unless I open the "page-worker" page(resource://...) purposely.
I think it will not be a good solution to open extension's page to let the user activate plugin.
Is there any good solution for my situation?
Thanks.
Powen

Sounds like a similar problem I've noticed. I get the click-to-activate pop-up on my chrome:// page which cannot be remembered since Firefox says the page name is (null)

[Georg Fritzsche]

If you have chrome privileges, you can activate the plugin yourself for now:
https://bugzilla.mozilla.org/show_bug.cgi?id=834918#c3

Georg

Post by powentan
Since Firefox 26 has decided to set "click to play" plugin by default, I have encountered a enabling plugin problem.
If the plugin is placed in the web page, either visible plugin or invisible plugin has a chance to enable it while navigating to that web page.
However, in my case, my plugin is placed in the extension's "sdk/page-worker" page, so there is no chance for the user to enable it unless I open the "page-worker" page(resource://...) purposely.

[powentan]

Georg Fritzsche於 2013年11月12日星期二UTC+8下午8時44分43秒寫道：

Post by Georg Fritzsche
https://bugzilla.mozilla.org/show_bug.cgi?id=834918#c3
Georg

Post by powentan
Since Firefox 26 has decided to set "click to play" plugin by default, I have encountered a enabling plugin problem.
If the plugin is placed in the web page, either visible plugin or invisible plugin has a chance to enable it while navigating to that web page.
However, in my case, my plugin is placed in the extension's "sdk/page-worker" page, so there is no chance for the user to enable it unless I open the "page-worker" page(resource://...) purposely.

Hi Georg,

It works perfectly.
I deeply appreciate your help!

Powen

[Paul Heil]

Post by Georg Fritzsche
https://bugzilla.mozilla.org/show_bug.cgi?id=834918#c3
Georg

Thanks too, I wouldn't have figured out how to do that for a while. Not sure about that "for now" part, but I'll take what I can get.

[Georg Fritzsche]

Post by Paul Heil

Post by Georg Fritzsche
https://bugzilla.mozilla.org/show_bug.cgi?id=834918#c3

Thanks too, I wouldn't have figured out how to do that for a while. Not sure about that "for now" part, but I'll take what I can get.

When bug 834918 is fixed, this shouldn't be needed anymore for plugins embedded in Chrome content - hence the "for now".

Georg

[powentan]

Georg Fritzsche於 2013年11月16日星期六UTC+8上午5時18分59秒寫道：

Post by Georg Fritzsche

Post by Paul Heil

Post by Georg Fritzsche
https://bugzilla.mozilla.org/show_bug.cgi?id=834918#c3

Thanks too, I wouldn't have figured out how to do that for a while. Not sure about that "for now" part, but I'll take what I can get.

When bug 834918 is fixed, this shouldn't be needed anymore for plugins embedded in Chrome content - hence the "for now".
Georg

Hi Georg,

The solution works on XUL-based extension.
But when it comes to the extension which uses firefox addon sdk, I encounter a problem.

My environment is Firefox 31 at Mac, and my extension will create NPAPI plugin on the sdk/page-worker.
The problem is if I want to use "obj.QueryInterface(Components.interfaces.nsIObjectLoadingContent).playPlugin()" to enable my NPAPI plugin, I need to use "Components.interfaces" and "QueryInterface" which are chrome privilege on firefox addon sdk.
And I don't find a way to use chrome privilege on page-worker page.
I also try to send NPAPI plugin object from page-worker page to main.js, but I also can't find a solution.

From my understanding, the page-worker should be a part of my extension, so if the user agrees to install my extension, NPAPI plugin should be whitelisted or there should be a way to enable it implicitly.

Is there any way to enable NPAPI plugin on page-worker page?

Powen

[Georg Fritzsche]

I suppose this is a restartless extension?
For that we have this bug open: https://bugzilla.mozilla.org/show_bug.cgi?id=989967
For non-restartless extensions you can bundle plugins and have them automatically activated already:
https://bugzilla.mozilla.org/show_bug.cgi?id=982101

There was some relevant discussion here:
https://bugzilla.mozilla.org/show_bug.cgi?id=931705

I don’t have experience with the addons SDK , so i’d suggest to ask on dev-extensions for further questions on the missing chrome privileges problem:
https://lists.mozilla.org/listinfo/dev-extensions

Georg

Post by powentan
Georg Fritzsche於 2013年11月16日星期六UTC+8上午5時18分59秒寫道：

Post by Georg Fritzsche

Post by Paul Heil

Post by Georg Fritzsche
https://bugzilla.mozilla.org/show_bug.cgi?id=834918#c3

Thanks too, I wouldn't have figured out how to do that for a while. Not sure about that "for now" part, but I'll take what I can get.

When bug 834918 is fixed, this shouldn't be needed anymore for plugins embedded in Chrome content - hence the "for now".
Georg

Hi Georg,
The solution works on XUL-based extension.
But when it comes to the extension which uses firefox addon sdk, I encounter a problem.
My environment is Firefox 31 at Mac, and my extension will create NPAPI plugin on the sdk/page-worker.
The problem is if I want to use "obj.QueryInterface(Components.interfaces.nsIObjectLoadingContent).playPlugin()" to enable my NPAPI plugin, I need to use "Components.interfaces" and "QueryInterface" which are chrome privilege on firefox addon sdk.
And I don't find a way to use chrome privilege on page-worker page.
I also try to send NPAPI plugin object from page-worker page to main.js, but I also can't find a solution.
From my understanding, the page-worker should be a part of my extension, so if the user agrees to install my extension, NPAPI plugin should be whitelisted or there should be a way to enable it implicitly.
Is there any way to enable NPAPI plugin on page-worker page?
Powen
_______________________________________________
dev-tech-plugins mailing list
https://lists.mozilla.org/listinfo/dev-tech-plugins

[powentan]

Georg Fritzsche於 2014年7月30日星期三UTC+8下午8時29分49秒寫道：

Post by Georg Fritzsche
I suppose this is a restartless extension?
For that we have this bug open: https://bugzilla.mozilla.org/show_bug.cgi?id=989967
https://bugzilla.mozilla.org/show_bug.cgi?id=982101
https://bugzilla.mozilla.org/show_bug.cgi?id=931705
https://lists.mozilla.org/listinfo/dev-extensions
Georg

Post by powentan
Georg Fritzsche於 2013年11月16日星期六UTC+8上午5時18分59秒寫道：

Post by Georg Fritzsche

Post by Paul Heil

Post by Georg Fritzsche
https://bugzilla.mozilla.org/show_bug.cgi?id=834918#c3

Thanks too, I wouldn't have figured out how to do that for a while. Not sure about that "for now" part, but I'll take what I can get.

When bug 834918 is fixed, this shouldn't be needed anymore for plugins embedded in Chrome content - hence the "for now".
Georg

Hi Georg,
The solution works on XUL-based extension.
But when it comes to the extension which uses firefox addon sdk, I encounter a problem.
My environment is Firefox 31 at Mac, and my extension will create NPAPI plugin on the sdk/page-worker.
The problem is if I want to use "obj.QueryInterface(Components.interfaces.nsIObjectLoadingContent).playPlugin()" to enable my NPAPI plugin, I need to use "Components.interfaces" and "QueryInterface" which are chrome privilege on firefox addon sdk.
And I don't find a way to use chrome privilege on page-worker page.
I also try to send NPAPI plugin object from page-worker page to main.js, but I also can't find a solution.
From my understanding, the page-worker should be a part of my extension, so if the user agrees to install my extension, NPAPI plugin should be whitelisted or there should be a way to enable it implicitly.
Is there any way to enable NPAPI plugin on page-worker page?
Powen
_______________________________________________
dev-tech-plugins mailing list
https://lists.mozilla.org/listinfo/dev-tech-plugins

Thanks for your information !

I have tried the solution in https://bugzilla.mozilla.org/show_bug.cgi?id=931705, but still not working.
So I post a question on mozilla.dev.extensions for further help.

Powen