Firefox和Chrome中的NPAPI支持实际上下降了？ [英] NPAPI support in Firefox and Chrome actually dropped?
问题描述
会发生什么？在2013年1月以后，我能在Chrome / Firefox中使用我的NPAPI插件吗？这是非常复杂的企业插件，所以我们想避免重新实现它。
从2014年1月起，Chrome将在Stable频道上阻止网页实例化的默认 NPAPI插件。
firefox dev的博客文章 b
$ b
为了让人们更好地控制他们浏览器，默认情况下，Firefox将不再激活大多数插件 。
我还发现了另一个贴子在Firefox Dev's Blog上说，我可以在Firefox Nightly中尝试新的插件管理系统。只需设置始终激活即可使插件正常工作。请问这种情况是否仍然存在？
短语默认阻止和不再默认激活一般来说，就像你链接到的最后一篇文章。也不会使用户无法使用NPAPI插件。他们将要求用户明确批准实例化NPAPI插件。然而，Chromium博客文章也表示：然而，最终NPAPI支持将从Chrome中彻底删除。 发生这种情况时，将无法在Chrome中加载NPAPI插件。
Recently I've found out that Chrome and Firefox are dropping NPAPI plugins support by January 2013. Anyway, reading the blog messages with more attention, it seems that NPAPI plugins will be just disabled by default and not actually impossible to use.
What will happen? Will I be able to use my NPAPI plugin in Chrome/Firefox after January 2013? It's pretty complex enterprise plugin, so we would like to avoid reimplementing it.
Starting in January 2014, Chrome will block webpage-instantiated NPAPI plug-ins by default on the Stable channel.
To give people more control over their browser, Firefox will no longer activate most plugins by default.
I've also found another post on Firefox Dev's Blog, saying that I can try new plugin management system in Firefox Nightly. It was enough to set "Always Activate" to make the plugin work. Will this remain this way?
The phrases "block by default" and "no longer active by default" are referring to things that look, in general, like the last post you linked to. Neither will make it impossible for users to use NPAPI plugins. They will require users to explicitly approve instantiation of NPAPI plugins.
However, the Chromium blog post also says: "Eventually, however, NPAPI support will be completely removed from Chrome." When that happens, it will be impossible to load NPAPI plugins in Chrome.
这篇关于Firefox和Chrome中的NPAPI支持实际上下降了？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
