Binary browser plugins using the 1990s-era NPAPI (“Netscape Plugin API”, the very name betraying its age) will soon be almost completely squeezed off the Web. Microsoft dropped NPAPI support in ...

Google Chrome recently dumped support for plugins such as Java and Silverlight, and now it’s Firefox’s turn. Late Thursday, Mozilla announced on its blog that Firefox would stop supporting plugins ...

Starting with March 7, when Mozilla is scheduled to release Firefox 52, all plugins built on the old NPAPI technology will stop working in Firefox, except for Flash, which Mozilla plans to support for ...

Join our daily and weekly newsletters for the latest updates and exclusive content on industry-leading AI coverage. Learn More Mozilla today launched Firefox 52 for Windows, Mac, Linux, and Android.

On Friday Oct. 9, Mozilla confirmed that by the end of 2016 the Netscape Plugin Application Programming Interface (NPAPI) will no longer feature plugin support in its browser. The concentrated efforts ...

Mozilla says it’s due to many of the services offered via NPAPI — like streaming video and clipboard access — are available as native Web APIs. In addition to ease and performance, Mozilla says NPAPI ...

Plug-ins based on the NPAPI architecture will be blocked by default in Chrome starting early next year as Google moves toward completely removing support for them in the browser. “NPAPI’s 90s-era ...

Starting in January 2015, Google’s Chrome browser will block all old-school Netscape Plug-In API (NPAPI) plugins. This doesn’t come as a huge surprise, given that Google started its efforts to remove ...

Google has shut down most plug-ins built for a decades-old architecture in the beta of Chrome 32, making good on a promise from September that it would nix NPAPI. NPAPI, for Netscape Plug-in ...