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

Chrome's built-in Flash plugin and PDF viewer are unaffected because they don’t use NPAPI. "NPAPI’s 90s-era architecture has become a leading cause of hangs, crashes, security incidents, and code ...

Reliant on plug-ins like Silverlight, Unity, and Java? Make plans to move on or change browsers, because most plug-ins will be banned from Chrome in the next year. Stephen Shankland worked at CNET ...

Google today removed apps and extensions that use the Netscape Plugin Application Programming Interface (NPAPI) from the Chrome Web Store home page, search results, and category pages. The company ...

A monthly overview of things you need to know as an architect or aspiring architect. Unlock the full InfoQ experience by logging in! Stay updated with your favorite authors and topics, engage with ...

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

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

Chrome's built-in Flash plugin and PDF viewer are unaffected because they don’t use NPAPI. "NPAPI’s 90s-era architecture has become a leading cause of hangs, crashes, security incidents, and code ...

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