On Wed, Jan 27, 2016 at 11:53 AM, Chuck Anderson <cra@xxxxxxx> wrote: > On Wed, Jan 27, 2016 at 06:41:55PM +0000, Richard Hughes wrote: >> On 27 January 2016 at 18:35, Stephen John Smoogen <smooge@xxxxxxxxx> wrote: >> > What can use the plugins if the major user no longer does? Don't the other >> > tools rely on xulrunner to use the plugons >> >> I'm kinda thinking of removing the PackageKit plugin from Fedora just >> because of this; if it exists and doesn't work, what's the point? > > So why is all this functionality being removed? What is supposed to > replace NPAPI, and can our plugins be modified to work with whatever > that new thing is? https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/ Not all plugins use NPAPI, but it looks like NPAPI support is going away (gone in Chrome already) and Mozilla is recommended all plugins use W3C Web APIs, or create an add-on. And in effect plugin support is also going away in Firefox, with a legacy exception for Flash. Add-ons have the ability to modify appearance and themes so that'd be the way forward for theming Firefox. But I'm guessing there's not much overlap for code reuse between a plugin using NPAPI and an Add-on. -- Chris Murphy -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
