DV Hardware - bringing you the hottest news about processors, graphics cards, Intel, AMD, NVIDIA, hardware and technology!

   Home | News submit | News Archives | Reviews | Articles | Howto's | Advertise
 
DarkVision Hardware - Daily tech news
November 17, 2018 
Main Menu
Home
Info
News archives
Articles
Howto
Reviews
 

Who's Online
There are currently 186 people online.

 

Latest Reviews
Arctic BioniX F120 and F140 fans
Jaybird Freedom 2 wireless sport headphones
Ewin Racing Champion gaming chair
Zowie P-TF Rough mousepad
Zowie FK mouse
BitFenix Ronin case
Ozone Rage ST headset
Lamptron FC-10 SE fan controller
 

Follow us
RSS
 

Google Chrome will no longer support Java due to phased out support for NPAPI

Posted on Wednesday, April 15 2015 @ 16:13:34 CEST by


Google logo
Last year Google's Chrome developers made the decision to phase out support for the deprecated NPAPI (Netscape Plugin Application Programming Interface) plugin architecture. It started via a whitelist system that only allowed a couple of trusted plugins to run by default but starting with the newly released Chrome 42, NPAPI is disabled by default. This may create a small support nightmare as there are unfortunately still a lot of outdated sites and services that require Java, especially in the government sector.

Users who absolutely need NPAPI can still enable it manually by toggling a flag in Chrome's settings menu but by September 2015 that option will disappear permanently. The big implication here is that Chrome will no longer support Oracle's Java, as that plug-in uses the outdated NPAPI architecture. It's unknown if Oracle has plans to rewrite its plug-in.
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.
Source: The Register



 



 

DV Hardware - Privacy statement
All logos and trademarks are property of their respective owner.
The comments are property of their posters, all the rest © 2002-2018 DM Media Group bvba