Google is going to traditional plug-ins in its Chrome browser out. Traditional plug-ins from the plug-in api from Netscape, but according to Google, is that is unsafe, unstable and too complex. By the end of 2014 is the support for the api fully be lwa is reached.
From now on it is no longer possible to have any plug-ins that the npapi use to add to the Chrome Web Store; from may, that is no longer discoverable, and from next year september all npapi plug-ins completely from the Chrome Web Store removed. At the end of next year in support of the Netscape Plug-in Api also complete the code of Chrome removed. Since then, other apis must be used to provide functionality such as that of the npapi to speak, as the native client interface of Chrome.
According to Google, the plug-in api does not have more of this time, and he makes for many crashes, freezes, security issues and more complex code. A lot of exploit kits such as BlackHole, use vulnerabilities in plug-ins like Java to pass unnoticed rogue software to install. The plug-in is transparently loaded, often without a user noticing.
Previously announced Firefox for all the plug-ins by default, block users, there should be a per-site opt for a plug-in to still activate. Firefox uses the same plug-in functionality as Chrome: that dates back to the nineties, and together with Netscape Navigator 2.0 was introduced. It was the first opportunity to be on the internet the other content to show than just text and static images. The use of npapi was powered by Adobe, that Acrobat software like in the browser wanted to run. Also Safari and Opera support npapi; Internet Explorer supported the api to the Service Pack 2 of version 5.5.