Google now provided an bring up to date on its arrangement to remove Netscape Plugin diligence encoding Interface (NPAPI) from Chrome, which the company says determination develop the browser’s security, zip, and stability, in the function of well in the function of reduce complexity taking part in the code station. Taking part in curt, the most recent timeline is in the function of follows: Bar all plugins by default taking part in January 2015, disable support taking part in April 2015, and remove support completely taking part in September 2015.
Intended for context, Google paramount announced taking part in September 2013 with the purpose of it was planning to drip NPAPI. Next to the phase, Google held undistinguished Chrome tradition data showed honest six NPAPI plugins were used by other than 5 percent of users, and the company was hopeful to remove support from Chrome “before the finish of 2014, but the exact timing determination depend on tradition and user reaction.”
While NPAPI tradition has continued declining since in that case, the drip has not been in the function of quick in the function of Google hoped. The most recent tradition data (for October 2014) shows the following launch percentages:
Silverlight (11 percent of Chrome users, down from 15 percent)
Google squeal (7 percent of Chrome users, down from 8.7 percent)
Java (3.7 percent of Chrome users, down from 8.9 percent)
Facebook film (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 tiny come to of trendy plugins at this time whitelisted and permissible by default taking part in Chrome (Silverlight is primarily used by Netflix users, but the company is little by little shifting to HTML5). Taking part in January 2015, Google diplomacy to remove the whitelist, blocking all plugins by default.
Users determination still be situated able to allow NPAPI plugins intended for detailed sites by clicking on the “Plug-in blocked” message taking part in the URL shaft and choosing “Always allow plug-ins on [website].” now is how with the purpose of looks:
Taking part in April 2015, this determination veto longer be situated an option in the function of NPAPI support determination be situated disabled by default taking part in Chrome and Google determination unpublish extensions requiring NPAPI plugins from the Chrome mesh amass. With the purpose of being held, Google determination provide an override intended for well along users (via an “enable-npapi” flag) and enterprises (via activity Policy) to in the short term re-enable NPAPI.
Google says this determination be situated needed as it expects a tiny come to of users determination still rely on plugins with the purpose of haven’t been ported to make use of alternative technologies. The two options determination be situated temporary workarounds in the function of a number of users delay intended for their “mission-critical” plugins to receive the transition.
Taking part in September 2015, Google determination scrap the workarounds and permanently remove NPAPI support from Chrome. NPAPI plugins determination simply veto longer load, not considering of whether they are wanted by websites before extensions.
It’s worth noting with the purpose of Google could just the once again delay its considered timeline intended for slaughter NPAPI, depending on how Chrome users react. On the other hand, if you still make use of solitary before other NPAPI plugins, you be supposed to look intended for alternatives.
Tags : Google
没有评论:
发表评论