The disabling of this feature will mean a large impact to several extensions and plugins that are available for the browser, such as Java. Chrome will now refuse to run the Java plugin as default.

Changing Web usage is hard. Google has granted a few extra months of leeway to those who rely on a handful of popular plug-ins, such as Silverlight, to extend what their browser can do.

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

Chrome 42, released to the stable channel today, will take a big step toward pushing old browser plugins, including Java and Silverlight, off the Web.

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.

Chrome, Firefox and Microsoft Edge have all either killed support for plugins, or announced that they’re going to do so in the near future, leaving no room to support the Java plugin.

The Java browser plugin, which allows certain applications to run in your browser, is being retired later this year. It was a common security vulnerability.

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.