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.

Google has turned off support for NPAPI in Chrome, disabling plugins such as Java.

Google Chrome 32 beta arrives with animated WebP, NPAPI plugins blocked by default, and faster touch input for Android November 21, 2013 - 7:10 pm ...

The SDK plugin add on currently supports the latest version of Chrome on Windows®. With this new HTML5 component, developers can use it alongside Dynamsoft's original ActiveX and NPAPI plugins, and ...

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

Google has announced it's killing off the Netscape Plugin Application Programming Interface (NPAPI) in Chrome, blocking the plugins from January 2014. Google said today it used anonymous Chrome ...

As outlined in the NPAPI Deprecation Guide, Chrome 42, which was due this month and was recently released to the stable channel, has disabled support for the Netscape Plug-in API. The reason is ...

Stating that “NPAPI’s 90s-era architecture has become a leading cause of hangs, crashes, security incidents, and code complexity”, Google intends to remove the Netscape Plug-in API. This is ...

In September Google released a 64-bit version of Google Chrome that did not include support for the Google Earth plugin or other NPAPI based plugins.

We told you in July about the Chrome team’s announcement last year that they planned to remove NPAPI support from Chrome by the end of 2014. This includes the Google Earth plugin that uses NPAPI ...