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

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

But it's been tough getting Chrome users to completely stop using those plug-ins. In September 2013, Google announced its plan to cut off support for NPAPI plug-ins.

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

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.

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

Those plugins use a 1990s-era API called NPAPI ("Netscape Plugin API") to extend the browser, and with Chrome 42, that API is now off by default.

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

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

The whitelist allowing popular NPAPI plugins to run within Chrome without user interaction will be removed at the start of next month.

Late Thursday, Mozilla announced on its blog that Firefox would stop supporting plugins based on the Netscape Plugin Application Programming Interface (NPAPI) architecture by the end of 2016.