The only permiting FLash (the plugin I would most like to kill) and not more useful ones like the Linux Gnome Shell Integration plugin makes it far more difficult to install gnome shell extensions. I realize this is listed as a Chrome parity bug, but that is the whole issue if chrome dropped support for this integration then our support for this is a differentiator in keeping our dominance in the preferred browser from many Linux Distributions.

Just to make it clear if the intent is to remove support for NPAPI plugins altogether (which I think it is) Then we should provide a pref like plugin.load_gnome_shell to permit loading this and work with the gnome shell team to come up with a real solution with an imposed deadline.

We are not going to change the plugin policy based on this request, so I'm going to move this into a Firefox component. I don't know what features are actually implemented by gnome shell integration, so it's hard to say what exact component this should go in or even who the right decision-maker is. Could you perhaps provide links or a more detailed description of what this feature is?

This is what allows you to go to the extensions.shell.org site and search for gnome shell extensions and install them via a click. IT is installed by default at least on fedora installations and is broken under Firefox 52.

What does the plugin *do*? If it's just exposing a special install API to the extensions.shell.org website, can this be implemented using a Firefox extension instead?

I am not sure if this could be an extension. It is not installing extensions to Firefox, it is is installing extensions to the gnome shell.

I would actually hope it would not be possible to do that via a Firefox extension.

I would actually hope it would not be possible to do that via a Firefox extension. It would seem to me that being able to alter the Operating system should not be possible via Firefox extensions.

Hmm and why are my bugs suddenly showing up as unconfirmed? last i Knew I had allowconfirm and allow edit which should permit my bugs to show up as new???????

OIC you changed it to unconfirmed??? Go figure.

I would appreciate my bugs not being changed to unconfirmed just because you don't understand the issue. That is what needinfo is for.

To make it clear the situation I am trying to avoid here is for the large number of Linux distros to each come up with a different unsupported way around this while they try to figure out what to do.. I kind of thought a unified approach would be better. That was my intent on filing this as a bug.

It seems like this can, and should work the same way as the Chrome extension: https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome. In fact, it looks like it should be pretty easy to port Firefox. That's going to be the way forward here, not enabling NPAPI work arounds.

Fine then I will do it on my own builds. I really did not want to do this.

By the way my nightly builds are published at http://www.wg9s.com/mozilla/firefox/

So the whole point of me filing this bug was to see if we could come up with a way to help them provide the functionality they used to have. It was NOT to provide NPAPI work arounds I guess some people cannot read.

(In reply to Bill Gianopoulos [:WG9s] from comment #16) > So the whole point of me filing this bug was to see if we could come up with > a way to help them provide the functionality they used to have. It was NOT > to provide NPAPI work arounds I guess some people cannot read. The functionality should already be provided by WebExtensions. Is there specific functionality beyond what's currently provided by WebExtensions that's missing that you're looking for a solution to?

If that functionality is provided via we extensions that is fine. I know nothing about this plug-in or how it works or what it needs. All I know is that with Firefox version 53 i can no longer install gnome shell extensions and when i visit the site to do so i get this.

INVALID is not a great word to describe the resolution of this bug, but that's the best I can do here. We (Mozilla) believe that plugins are not the right technology for this, so we'd WONTFIX any plugin-based solutions. We believe that WebExtensions are the correct solution, and transitioning to that is the responsibility of the extensions.gnome.org team.

I object violently to this being closed as invalid. The decision here violates principle number 5 of the Mozilla manifesto "Individuals must have the ability to shape the Internet and their own experiences on it." it should be up to the user to determine which plugins are useful and should be loaded despite the direction to get away from supporting NPAPI plugins. If you wish to close this please close ans WONTFIX with enough comment to justify violating this principle.

As both Benjamin and Jeff said, extensions.gnome.org can simply switch to an extension, instead of a NPAPI plugin. Indeed, they are already working on it: https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome/RoadMap.

(In reply to Marco Castelluccio [:marco] from comment #21) > As both Benjamin and Jeff said, extensions.gnome.org can simply switch to an > extension, > instead of a NPAPI plugin. > Indeed, they are already working on it: > https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome/RoadMap. That is a much better answer and a more acceptable close reason.

I'm uploaded experimental version of GNOME Shell integration extension to a.m.o. a couple of days ago: https://addons.mozilla.org/ru/firefox/addon/gnome-shell-integration/ It's currently at validation by Mozilla staff. You can track chrome-gnome-shell's Firefox support status at https://bugzilla.gnome.org/show_bug.cgi?id=754316

(In reply to Yuri Konotopov from comment #23) > I'm uploaded experimental version of GNOME Shell integration extension to > a.m.o. a couple of days ago: > https://addons.mozilla.org/ru/firefox/addon/gnome-shell-integration/ > It's currently at validation by Mozilla staff. > You can track chrome-gnome-shell's Firefox support status at > https://bugzilla.gnome.org/show_bug.cgi?id=754316 Good try, but this needs to be something installed when you visit the Gnome Shell Extensions page. It is a who do you trust to install Gnome Shell Extensions. It is NOT a mozilla.org website.

> Good try, but this needs to be something installed when you visit the Gnome Shell Extensions page You can follow inline installation of Chrome/Opera/Firefox extensions from e.g.o. at https://bugzilla.gnome.org/show_bug.cgi?id=771241 It's my short term task for e.g.o. and chrome-gnome-shell.