Google Chrome 42 disables NPAPI support by default, and Project Spartan lacks ActiveX support entirely. Both of these changes prevent the use of Java in either browser.

Java The Java browser plug-in lets Chrome run applets, small programs embedded in a Web page. Java applets enable dynamic Web pages and interactive web programs.

Choose Plugins in the left pane, scroll to the entry for the Java plug-in, and click its Disable button. Disable Firefox's Java plug-in via the browser's Add-on Manager.

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.

NPAPI plug-ins were blocked since January 2014, but some of the popular ones were whitelisted, including Java, Unity, Silverlight, Facebook Video, and a couple of others.

Plug-ins can open vulnerabilities in even relatively secure browsers like Chrome. Even coders, like Jeff Atwood, can fall victim. Here's how to reign in plug-ins like Java, or disable them ...

Oracle has announced that it will kill the much-maligned Java browser plugin in the next release of the Java Development Kit, slated for release next year.

Oracle has finally announced its intent to nail the coffin shut on its Java browser plugin.

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.

Java, used by 8.9% of Chrome users, will not be whitelisted by default because it is already blocked for security reasons. Other NPAPI-based plugins can be enabled on a case-by-case basis by the user.