With the release of Chrome 42 this week, Google fixed more than 40 vulnerabilities. But the most significant security change in the new browser is Google’s decision to disable the NPAPI, essentially ...

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 ...

Mozilla in four weeks will bar plug-ins built using a decades-old technology from Firefox, ending a years-long process designed to make the browser more secure. The single exception to the ban: ...

A week after releasing the stable version of Chrome 31, Google has announced more features coming to Chrome 32 beta for Windows, Mac, Linux, and Android. In addition to indicators for tabs, the new ...

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 ...

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 ...

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 ...

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 ...