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 42, released to the stable channel today, will take a big step toward pushing old browser plugins, including Java and Silverlight, off the Web.

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.

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

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.

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.

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.

With the demise of Adobe Flash on the way, Oracle has announced via a very short blog post that come JDK 9 later this year, the Java browser plugin will be deprecated.

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.

Chrome disabled support in September for plug-ins that, like Java and Silverlight, use the old Netscape Plugin Application Programming Interface (NPAPI) standard.