
In the absence of any other factors you should probably set this to be your most recent JDK version. The one you refer to on the path is your choice - but presumably you'd choose the one that you want to use whenever you type "java. You can install as many JDKs as you like. All code shall run within sandbox with limited access to the file system and such.Īlso as the plugin check for installed JRE version at your machine, that means you do have JRE. Since the plugin installs the JRE, this key is set to a JRE path and therefore needs to be edited if you want Chrome to work with the JDK. There are limitations when running Java code with the Java plugin for security reasons. Apparently, Chrome addresses a key in Windows registry when it looks for a Java Environment. The main entry point class must be written as an Applet when the plugin is used, but all the Java code it calls can be just regular Java. The plugin is bundled with the JRE, and runs inside a browser, allowing Java code to run inside the browser process on the client. You can check the Java plugin of Chrome browser in this link. The Java browser plugin is the bridge between the JRE and the browser, used to run Java classes of applets embedded in HTML. the software you need to interpret and execute Java class files. You must restart Google Chrome to enable the changes after a refresh. You must click Apply and then OK to confirm the changes. I've been trying to install the Java plugin for Chrome for a couple hours now, and I figured it was time to ask people with more experience. Java content can be enabled by clicking Enable Java content from here.

I am hoping by that time some patch will be added.The JRE is the Java Runtime Environment, i.e. How Do I Enable Java In Google Chrome In Java Control Panel, select Security from the list of options. Chrome 34 doesn't have any glaring bugs, so you can use it safely for the next 3 months. Then use synaptic package manager or use the commandline to lock upgrades for google-chrome-stable package.


To all of you: To keep Chrome functioning, please downgrade your GOogle Chrome to 34. You guys can start a discussion on that thread. Here it is : Ī relevant question was posted to Oracle. My bug report was merged into the parent bug and it's been set as won't fix. Looks like we are going to be stuck here for quite a while. You can try and follow the thread for this discussion here: !topic/chromium-dev/圎bgvWE7wMk Awaiting a proper response from the devs. As other folks have mentioned, Java, ActiveX, Silverlight, Browser Helper Objects (BHOs) and other plugins are not supported in Microsoft Edge.

Its because of the removal of the older plugin NPAPI. You cannot get Java to work on Chrome 35.
