什么是Firefox扩展和插件的区别？ [英] What is The difference between Firefox extension and plugin?

问题描述

在Firefox中有插件和扩展。你能向我解释为什么这些插件有不同的名称和标签？他们有很大的不同，所以他们需要不同的名字？我认为这些东西有点不自然，扩展有如此多的功能，他们缺少什么与插件进行比较的方式？ 解决方案

p>这个差别既是历史的，也是真实的：

• 插件是可编译的，可加载的模块，最初来自 NPAPI ;他们可以在浏览器的进程空间之外生活（这会导致各种有趣的互操作性问题和可能性）。最常见的例子是Flash和Java--它们都要求一个子窗口（viewport或canvas（不是HTML5的 canvas ） - 这完全是另一回事：网页的一部分）），并以自己的方式进行处理，主要独立于浏览器。
/en.wikipedia.org/wiki/XULrel =noreferrer> XUL 。由于扩展作为浏览器的一部分，它们具有比JS-in-a-page更广泛的访问权限，但是它们仍然受到某些限制。最常见的整合方式是挂钩FF功能的某些部分，然后扩展它。


所以，尽管插件和扩展可能会相互关联，但它们在后台是非常不同的技术。

In Firefox there are plugins and extensions. Could you please explain to me why these addons have different name and tabs ? Does they differ so much so they need different names? I think it's a little unnatural to differ these things, extensions have so much and more functionality, what they lack for comparing to plugins?

解决方案

The difference is both historical and real:

• plugins are compiled, loadable modules, originally descended from NPAPI; they can live outside of the browser's process space (which leads to all kinds of fun interoperability issues and vulerabilities). The most common examples of these are Flash and Java - both request a sub-window ("viewport" or "canvas" (not HTML5's canvas - that's something else altogether: a native part of the webpage)) inside the webpage and handle it themselves, in a way that's largely independent of the browser.
• extensions are written mostly in JavaScript and XUL. Since the extensions act as part of the browser, they have wider access privileges than JS-in-a-webpage, but they are still subject to some limitations. The most common way of integration is to hook into some part of FF's functionality and extend it.

So, although the plugins and extensions might appear to be related, they're very different technologies behind the scenes.

这篇关于什么是Firefox扩展和插件的区别？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！