The name “Netscape Plug-in API” (NPAPI) sounds like a relic from another age of browsers, but Chrome, Mozilla and other browsers still support this architecture for writing browser plug-ins today. But ...

Google plans to completely remove support for the popular Netscape Plug-in APIs from Chrome by the end of 2014 Plug-ins based on the NPAPI architecture will be blocked by default in Chrome starting ...

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

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

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

Plug-ins like Silverlight and Google Earth will be harder to find in the Chrome Web Store as Google works to build a safer, faster Web browser. Seth Rosenblatt Former Senior Writer / News Senior ...

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