No word on porting the Java plug-in to use the Native Client. Among others, they suggest switching to Firefox, IE or Safari. DO Not upgrade chrome browsers to version 42.or Java plugins will not work. One of my users advised me images were not showing up using java in the Chrome browser.
Update. After the publishing of this article, Oracle has provided instructions on using Java on Chrome 42. Get answers from your peers along with millions of IT pros who visit Spiceworks. We have not heard of any plans from Oracle or Microsoft intending to port their plug-ins to use Chrome’s Native Client. Nonetheless, Mozilla mentions on their developer site that “plug-ins are now a legacy technology” and advises website developers to “avoid using plugins wherever possible”. NPAPI is still used by several Mozilla projects, including Firefox, and Apple’s Safari. This solution will work until September when support for NPAPI will be completely removed from Chrome. Mac OS and Windows users can enable NPAPI through its flag on the chrome://flags/ page, and enterprise administrators are still able to whitelist related plug-ins through the EnabledPlugins policy list. Now, the NPAPI itself is disabled, and the plug-ins using it no longer appear on the chrome://plugins/ page. In January 2015, the respective plug-ins were blocked by default, but the user could enable them for specific websites. 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. The reason is that NPAPI “has become a leading cause of hangs, crashes, security incidents, and code complexity” and the intent was first announced in 2013. I am hoping by that time some patch will be added.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. 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.
Back How to enable the PDF plugin in Chrome. Choose 'Enable plug-ins' and 'Enable java', hook on. Here it is : Ī relevant question was posted to Oracle. From the resulting drop-down menu, choose Manage Add-ons, followed by Enable Add-ons. 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. Its because of the removal of the older plugin NPAPI. You cannot get Java to work on Chrome 35.
0 kommentar(er)
