more quick actions
minimize quick actions
Old
3
Posts
2
Users
0
Likes
55
Views
Hi guys,
As most of you probably knew, Chrome has announced that they will stop supporting Java applet by disabling deprecated NPAPI (Netscape Plug-in API) support that is required to run JRE plugin. So ,even though our machine has JRE installed and other browsers (IE, Firefox) can detect JRE, chrome will not be able to run it by default.
The question is, I know that we're moving WebVue away from Java and in the future will support HTML5, but do you guys have any idea on how to tackle this issue or probably the developer themselves have come with a workaround to support our existing WebVue users? I mean even after Sept 2015 (the target end date), there will be people who will still insists on running WebVue from Chrome and the fact that we still have a large customer base that we need to support running existing and prior versions of PcVue (WebVue). Thanks
http://javatester.org/ - Java security news
To test you can type:
chrome://plugins/ - to see if JRE plugin is detected
Althought for time being there is a work around but Oracle Java is advising people to use other browsers instead. We may want to advise our customer about this.
https://www.java.com/en/download/faq/chrome.xml
---------------------------------------------------------------------------
NPAPI support by Chrome
The Java plug-in for web browsers relies on the cross platform plugin architecture NPAPI, which has long been, and currently is, supported by all major web browsers. Google announced in September 2013 plans to remove NPAPI support from Chrome by "the end of 2014", thus effectively dropping support for Silverlight, Java, Facebook Video and other similar NPAPI based plugins. Recently, Google has revised their plans and now state that they plan to completely remove NPAPI by late 2015. As it is unclear if these dates will be further extended or not, we strongly recommend Java users consider alternatives to Chrome as soon as possible. Instead, we recommend Firefox, Internet Explorer and Safari as longer-term options.
---------------------------------------------------------------------------
The workaround, pls follow the instructions – probably until Sept 2015 before new Chrome update
https://www.java.com/en/download/faq/chrome.xml#npapichrome
---------------------------------------------------------------------------
In April 2015 (Chrome 42) NPAPI support will be disabled by default in Chrome and we will unpublish extensions requiring NPAPI plugins from the Chrome Web Store. All NPAPI plugins will appear as if they are not installed, as they will not appear in the navigator.plugins list nor will they be instantiated (even as a placeholder). Although plugin vendors are working hard to move to alternate technologies, a small number of users still rely on plugins that haven’t completed the transition yet. We will provide an override for advanced users (via chrome://flags/#enable-npapi) and enterprises (via Enterprise Policy) to temporarily re-enable NPAPI (via the page action UI) while they wait for mission-critical plugins to make the transition. In addition, setting any of the plugin Enterprise policies (e.g. EnabledPlugins, PluginsAllowedForUrls) will temporarily re-enable NPAPI.
---------------------------------------------------------------------------
chrome://flags/#enable-npapi
rgds
Posted : 26/06/2015 7:07 am
Thanks for your explanations, Irwan.
I confirm that WebVue (e.g. the WebVue Java applet) no longer works with Chrome 45 and later versions. Furthermore npapi can no longer be enabled manually in Chrome 45.
Please see below the official statement from Google:
In the past, many plugins were developed using an old system called NPAPI. Today fewer sites are using NPAPI plugins and they have often caused security risks on websites.
To make browsing with Chrome safer, faster, and more stable, we stopped allowing NPAPI plugins on September 1, 2015.
Plugins that use NPAPI, including Silverlight, Java, and Unity, won’t work. If you want to use a website that uses an NPAPI plugin, you’ll need to use a different web browser.
(Source: https://support.google.com/chrome/answer/6213033?hl=en )
There are three options to solve the problem:
- If the customer insists on using Google Chrome, install Chrome 44, enable npapi manually and diabled automatic updates (not recommended!).
- Ask the customer to use a different web browser, Mozilla Firefox, for example.
- Convince the customer to run WebVue outside of the web browser context as Java web start application (click-once-deployment). As we can assume that other browser vendors may possibly follow Google's move and disable support for Java applets, this is probably to be regarded as the most appropriate and sustainable solution. For details please check the attached file.
Posted : 24/09/2015 1:55 pm
As already expected in my previous post the NPAPI-domino continues:
Mozilla is about to drop NPAPI for Firefox.
https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/
By the way, there is an interesting note by the end of the text saying "Oracle recommends that sites currently using Java applets consider switching to plugin-free solutions such as Java Web Start".
Posted : 12/10/2015 1:26 pm