Google in our day provided an modernize on its graph to remove Netscape Plugin hard work encoding Interface (NPAPI) from Chrome, which the company says yearn for further the browser’s security, hustle, and stability, to the same degree well to the same degree reduce complexity participating in the code starting point. Participating in brief, the most modern timeline is to the same degree follows: Hinder all plugins by default participating in January 2015, disable support participating in April 2015, and remove support completely participating in September 2015.
In support of context, Google chief announced participating in September 2013 to it was planning to ooze NPAPI. Next to the moment, Google held dull Chrome practice data showed recently six NPAPI plugins were used by additional than 5 percent of users, and the company was hopeful to remove support from Chrome “before the halt of 2014, but the exact timing yearn for depend on practice and user reaction.”
While NPAPI practice has continued declining since it follows that, the ooze has not been to the same degree quick to the same degree Google hoped. The most modern practice data (for October 2014) shows the following launch percentages:
Silverlight (11 percent of Chrome users, down from 15 percent)
Google chat (7 percent of Chrome users, down from 8.7 percent)
Java (3.7 percent of Chrome users, down from 8.9 percent)
Facebook videotape (3 percent of Chrome users, down from 6 percent)
Unity (1.9 percent of Chrome users, down from 9.1 percent)
Google Earth (0.1 percent of Chrome users, down from 9.1 percent)
The exceeding six are part of a insignificant integer of accepted plugins at this time whitelisted and permitted by default participating in Chrome (Silverlight is primarily used by Netflix users, but the company is leisurely shifting to HTML5). Participating in January 2015, Google tactics to remove the whitelist, blocking all plugins by default.
Users yearn for still be there able to allow NPAPI plugins in support of limitation sites by clicking on the “Plug-in blocked” message participating in the URL pole and choosing “Always allow plug-ins on [website].” now is how to looks:
Participating in April 2015, this yearn for refusal longer be there an option to the same degree NPAPI support yearn for be there disabled by default participating in Chrome and Google yearn for unpublish extensions requiring NPAPI plugins from the Chrome complication lumber room. To being held, Google yearn for provide an override in support of cutting edge users (via an “enable-npapi” flag) and enterprises (via activity Policy) to in the interim re-enable NPAPI.
Google says this yearn for be there essential for the reason that it expects a insignificant integer of users yearn for still rely on plugins to haven’t been ported to treatment alternative technologies. The two options yearn for be there temporary workarounds to the same degree a quantity of users linger in support of their “mission-critical” plugins to make up the transition.
Participating in September 2015, Google yearn for scrap the workarounds and permanently remove NPAPI support from Chrome. NPAPI plugins yearn for simply refusal longer load, no matter what of whether they are required by websites or else extensions.
It’s worth noting to Google can on one occasion again delay its premeditated timeline in support of carnage NPAPI, depending on how Chrome users react. Nonetheless, if you still treatment solitary or else additional NPAPI plugins, you ought to look in support of alternatives.
Tags : Google
没有评论:
发表评论