Updating foxfire plugins

The Mozilla team wants to work closely with affected publishers to make this transition as painless as possible.The Web provides an increasingly rich environment which should eliminate the need for plugins, and we are eager to continue improving the Web platform for any use cases where plugins may still be required.It is hard to keep the site running and producing new content when so many people block ads.

updating foxfire plugins-70updating foxfire plugins-35updating foxfire plugins-38

The Java Plugin for web browsers relies on the cross-platform plugin architecture NPAPI, which had been supported by all major web browsers for over a decade.

The 64 bit version of Firefox has never supported NPAPI, and Firefox version 52ESR is the last release to support the technology.

Plugins are a source of performance problems, crashes, and security incidents for Web users.

Mozilla intends to remove support for most NPAPI plugins in Firefox by the end of 2016.

Features such as clipboard access which used to require plugins are now available via native Web APIs.

As browsers and the Web have grown, NPAPI has shown its age.Firefox began this process several years ago with manual plugin activation, allowing users to activate plugins only when they were necessary.This decision mirrors actions by other modern browsers, such as Google Chrome and Microsoft Edge, which have already removed support for legacy plugins.Site maintainers should prepare for plugins to stop working in all versions of Firefox by the end of 2016.Mozilla continues to work with the Oracle Java Platform Group to ensure a smooth transition for those web sites that use Java.Discussion about this announcement and any questions about the future of Firefox plugins should be directed to the Mozilla plugins development list.

Tags: , ,